> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/monitors/{monitor_id}

> Retrieve a single monitor by id

Retrieve a single monitor by id

<Info>
  Audience: application and coding agent.
</Info>

## Before you act

Read the current `searchMode`, `filters`, `delivery.status`, `isActive`, and `lastCheckedAt` before replacing a destination or diagnosing a missing alert. A monitor belongs to its organization; an unknown or out-of-scope id returns `404`.

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/monitors/mon_example_123"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Call SEC API GET /v1/monitors/{monitor_id} to inspect the saved query, filters, active state, delivery configuration, and last checked timestamp before changing a monitor or interpreting its matches.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff