Create a monitor.
Monitors run on a fixed frequency to detect material changes in web content.
Set type=event_stream to monitor a search query, or type=snapshot to
monitor a specific task run’s output. The monitor runs once immediately at
creation, then continues on the configured schedule.
Documentation Index
Fetch the complete documentation index at: https://docs.parallel.ai/llms.txt
Use this file to discover all available pages before exploring further.
Request body to create a monitor.
The type field at the root determines the expected shape of settings:
event_stream requires MonitorEventStreamSettings, and snapshot
requires MonitorSnapshotSettings.
Type of monitor to create. event_stream monitors a search query for material changes; snapshot monitors a specific task run's output. Determines the expected shape of settings.
event_stream, snapshot "event_stream"
"snapshot"
Frequency of the monitor. Format: '' where unit is 'h' (hours), 'd' (days), or 'w' (weeks). Must be between 1h and 30d (inclusive).
"1h"
"12h"
"1d"
"7d"
"30d"
Type-specific settings for an event_stream monitor.
Processor to use for the monitor. lite is faster and cheaper; base performs more thorough analysis at higher cost and latency. Defaults to lite.
lite, base Webhook to receive notifications about the monitor's execution.
User-provided metadata stored with the monitor and echoed back in webhook notifications and GET responses, so you can map events to objects in your application. Keys: max 16 chars; values: max 512 chars.
{
"slack_thread_id": "1234567890.123456",
"user_id": "U123ABC"
}Monitor created successfully.
Response object for a monitor.
The type field at the root determines the concrete shape of settings:
event_stream uses MonitorEventStreamResponseSettings, and snapshot
uses MonitorSnapshotResponseSettings. Snapshot monitors also carry an
output field (MonitorSnapshotOutput) with the latest computed state.
The type of monitor.
event_stream, snapshot "event_stream"
"snapshot"
ID of the monitor.
Status of the monitor.
active, cancelled "active"
"cancelled"
Frequency of the monitor. Format: '' where unit is 'h' (hours), 'd' (days), or 'w' (weeks). Must be between 1h and 30d (inclusive).
"1h"
"12h"
"1d"
"7d"
"30d"
Processor to use for the monitor. lite is faster and cheaper; base performs more thorough analysis at higher cost and latency. Defaults to lite.
lite, base "lite"
"base"
Timestamp of the creation of the monitor, as an RFC 3339 string.
"2025-01-15T10:30:00Z"
Type-specific response fields for an event_stream monitor.
Webhook configuration for the monitor.
User-provided metadata stored with the monitor and echoed back in webhook notifications and GET responses, so you can map events to objects in your application. Keys: max 16 chars; values: max 512 chars.
{
"slack_thread_id": "1234567890.123456",
"user_id": "U123ABC"
}Timestamp of the last run for the monitor, as an RFC 3339 string.
"2025-01-15T10:30:00Z"
Runtime output state. Present only for snapshot monitors; null for event_stream monitors.