Create a Monitor
Creates a new Monitor to run recurring Exa searches on a schedule.
Monitors automatically execute your search query on a recurring schedule and deliver results to your webhook endpoint with automatic deduplication:
-
Date-based filtering only fetches content since the last run
-
Semantic deduplication tracks previous outputs to surface only new developments
The response includes a webhookSecret that is only returned once at creation time. Store it securely for webhook signature verification.
Documentation Index
Fetch the complete documentation index at: https://exa.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer .
Body
An optional name for the monitor
Controls the format of the run output. Defaults to { "type": "text" } if not specified. When type is "text", the output is a plain text summary. When type is "object", the output is structured JSON. If no properties are specified with "object" type, a schema is inferred automatically; otherwise the output adheres to the provided schema.
- Option 1
- Option 2
Optional key-value metadata. Echoed back in webhook deliveries so you can route updates to systems like Slack.
{
"slack_channel_id": "C123ABC",
"slack_thread_id": "1745444400.123456",
"user_id": "U123ABC"
}Response
The created monitor with webhook secret
The unique identifier for the monitor
An optional display name
The status of the monitor. active monitors run on schedule and can be triggered manually. paused monitors can only be triggered manually. disabled monitors are auto-disabled after 10 consecutive authentication failures.
active, paused, disabled The interval-based schedule for automatic runs. Null if no schedule is set.
Controls the format of the run output. Defaults to { "type": "text" } if not specified. When type is "text", the output is a plain text summary. When type is "object", the output is structured JSON. If no properties are specified with "object" type, a schema is inferred automatically; otherwise the output adheres to the provided schema.
- Option 1
- Option 2
Optional key-value metadata for your own tracking. Echoed back in webhook deliveries so you can route updates to systems like Slack.
{
"slack_channel_id": "C123ABC",
"slack_thread_id": "1745444400.123456",
"user_id": "U123ABC"
}When the next scheduled run will occur. Null if no trigger is set.
When the monitor was created
When the monitor was last updated
The secret used to verify webhook signatures. This is only returned once at creation time. Store it securely.

