# Check for paradoxes in a timeline

Endpoint: POST /paradox-checks
Version: 1.0.0
Security: bearerAuth

## Request fields (application/json):

  - `timeline_id` (string)
    Example: "tml_tesla_mission_1"

  - `proposed_changes` (array)
    Example: [{"event":"Retrieve Tesla's Blueprint","time":"1889-03-10T23:50:00Z"},{"item_id":"itm_tsla_blueprint"}]

## Response 200 fields (application/json):

  - `is_stable` (boolean)
    The stability status of the timeline
    Example: true

## 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"