Preview Monitor
Executes one on-demand Preview of the same standing question that POST /api/v2/monitors accepts, without saving, enabling or delivering it. Browser and API-key calls have the same non-delivering behavior. Body field history_days=7 (default) or 30 returns setup_preview: matching records by type, active/quiet days, busiest day, representative evidence and cadence-based notification estimates. Missing or partial history is explicit. Query subjects preserve descriptor-validated filters and return executed_requests; setup_executed_requests capture their historical reads. For Event, Story and Entity query setup previews, query_window identifies inclusive reporting dates with time_basis=endpoint_default; the historical matching estimate does not replay recorded additions or notifications, and evaluation.would_trigger is false with no new-item claim. Activity query previews retain their recorded interval and explicit publication-source coverage; unavailable history is never replaced with reporting examples. Query Monitors match newly available committed records, including late arrivals; preview dates and source_request dates never control scheduled matching. Top-level window_start/window_end retain the half-open preview interval; window_label names historical setup estimates and must not be used as query matching dates. An accepted Preview costs 1 QU; authentication, validation, plan and internal execution failures cost 0. Scheduled Monitor executions cost 0. An empty configured window may include a separately labelled historical_example using the same filters over an expanded 30-day period; it never changes the actual evaluation or trigger state. Query work has a 45-second deadline measured from request entry. The optional historical example uses at most 10 seconds within the remaining budget; historical_example_status=unavailable means that example could not complete, not that no historical matches exist. criteria.data selects ONE lane: events for coded incidents or stories for coverage clusters, defaulting to events. events_and_stories is DEPRECATED as of 2026-09-01 and is no longer offered to new Monitors. It is still accepted and still runs both lanes, so saved Monitors and existing integrations are unaffected and will not be removed before 2026-10-01. Both lanes in one Monitor contend for the same warehouse, so a slow Story lane fails the whole Monitor including an events half that already returned. Measured in production: 35.1 s mean against 25.5 s for events and 26.3 s for stories, and every reproducible 503 in a 40-request Preview sweep was a both-lanes specification. Choose events for incident questions or stories for coverage questions, and create a second Monitor when you genuinely want both — two Monitors fail independently, and their match counts do not double-count an incident that appears as both a Story and its Event. Takes no query parameters, so a query-string typo can no longer ride along on a charged call.
Authorizations
GDELT Cloud API key. Send as Authorization: Bearer gdelt_sk_....
Body
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
Preview history: 7 or 30 days, default 7. Display only; scheduled matching starts at first enablement and follows the previous successful checkpoint.
7 Preview never sends notifications. email may be false and webhook_url may be omitted; no saved delivery is created.

