# Monitor a timeline for anomalies

Endpoint: GET /monitor-timeline
Version: 1.0.0
Security: bearerAuth

## Query parameters:

  - `timeline_id` (string, required)
    The ID of the timeline to monitor

## Response 200 fields (application/json):

  - `status` (string)
    The status of the timeline monitoring operation

  - `anomalies` (array)

  - `anomalies.anomaly_id` (string)
    Unique identifier for the detected anomaly

  - `anomalies.description` (string)
    Details of the anomaly detected in the timeline

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