Skip to main content
A monitor saves a set of searches, re-runs them on a cadence, and hands you only what it has not delivered before. Start by creating one. The monitor begins running as soon as it exists.
The name is unique per organization among live monitors. A search request takes the same filters as a one-off search — see Filter by date. Once the first run has finished, read the records it produced. Records are returned oldest first, one page at a time. To read them all, page with since as shown in Read records.

Next steps

To learn more about Seltz Monitor, check out the following topics:
  • Concepts — Monitors, runs, records and webhooks
  • Read records — Paging and streaming what the monitor produces
  • Webhooks — Being told when a run finishes
  • Inspect runs — Reading run history and per-request health
  • Manage monitors — Listing, updating, pausing and deleting
  • Reference — Endpoints, SDK methods, limits and errors