# Travel across time

Travel to a timeline or to a temporal anchor to return.

Endpoint: POST /travels
Version: 1.0.0
Security: bearerAuth

## Request fields (application/json):

  - `destination` (string, required)
    The ID of the destination timeline or anchor
    Example: "tml_tesla_mission_1"

  - `items_transported` (array)
    List of items successfully transported during time travel
    Example: ["itm_tsla_blueprint"]

## Response 200 fields (application/json):

  - `destination` (string, required)
    The ID of the destination timeline or anchor
    Example: "tml_tesla_mission_1"

  - `arrival_time` (string)
    The exact time of arrival at the destination
    Example: "1889-03-10T23:50:00Z"

  - `items_transported` (array)
    List of items successfully transported during time travel
    Example: ["itm_tsla_blueprint"]

## Response 400 fields (application/problem+json):

  - `type` (string)
    A URI reference that identifies the problem type.
    Example: "https://api.warp.example.com/problems/invalid-request"

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Invalid Request"

  - `status` (integer)
    The HTTP status code.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The request payload is not valid according to the schema."

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/problems/invalid-request/1234"