# Manipulate an event in a timeline

Endpoint: POST /events
Version: 1.0.0
Security: bearerAuth

## Request fields (application/json):

  - `timeline_id` (string, required)
    The ID of the timeline where the event will be manipulated

  - `event_id` (string, required)
    The ID of the event to manipulate

  - `new_outcome` (object, required)
    The details of the new outcome for the event

  - `new_outcome.description` (string)
    A description of the new event outcome

  - `new_outcome.changes` (array)

  - `new_outcome.changes.action` (string)
    The action to take for the event

  - `new_outcome.changes.time` (string)
    The new time for the event

## Response 200 fields (application/json):

  - `status` (string)
    Status of the event manipulation operation

  - `new_event_id` (string)
    The ID of the newly created event after manipulation

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