Monitors
List results
List a monitor’s results with GET /v1/monitors//results: every result it accepted, newest first, one per story, filtered by importance.
GET
TypeScript
List the monitor’s results, every page it accepted, newest first, whether or not a run or webhook delivered it. To read a monitor without a webhook or schedule, poll this endpoint and stop at the first
Replace
id you’ve already seen.
When to use it
Use it when you have no public endpoint for a webhook and no schedule, or to look back over results a run or webhook already gave you. Passmin_importance=4 to keep only the results not to be missed. This request returns them:
mon_123 with your monitor’s id. You get the results in data, newest first. Each one has a summary, an importance from 1 to 5, and same_story, the number of pages on the same story that were left out. Store the first id and stop at it on the next poll. An empty data on a new monitor is expected: it matches only pages crawled after it was created.
SDK, CLI and MCP
The SDK methods need SDK 0.2.0 or later. See SDKs → Monitors, CLI → Monitors and Monitors tools.
Related operations
- List runs shows the same results grouped by the run that returned them.
- Read the results compares webhooks, runs and polling.
- Create a monitor with
search.content.textto add each page’s text.