Skip to main content
Monitors are saved filing searches for a defined alert job: for example, 8-Ks for a five-issuer watchlist or amendments to a specific form. A monitor match is a signal to inspect a filing, not an assertion that the filing is material.

​
Configure the monitor with a human session

Create, edit, pause, and delete monitors from the signed-in SEC API dashboard. These are organization control-plane actions and require a WorkOS browser session. API keys and autonomous agents cannot create or alter them. For one bounded job, set a descriptive name, keyword query, ticker/form filters, and one delivery destination. Use email for a human inbox. Use an organization webhook endpoint subscribed to monitor.match for an application receiver.

​
Preview before waiting for delivery

API keys can read monitor data after setup. Preview the saved query before you rely on the scheduled dispatch:
Expected output is the current matching filing set, plus response correlation fields when returned. This on-demand read does not send an email or webhook. Keep each match’s accession number, filing date, ticker, form, source URL, and the response requestId with your alert record.

​
Delivery and limits

Active monitors run on a 15-minute cadence. A typical alert arrives about half a sweep after a new matching record becomes available; worst case is one sweep plus delivery time. This is scheduled monitoring, not an instant EDGAR feed. Transient email failures retry automatically. The default delivery limits are 100 sends per monitor per hour and 1,000 per organization per day. Narrow a noisy query, split unrelated jobs, and make the receiver idempotent rather than assuming every event is unique.

​
Investigate failures

  • No preview matches: check query terms, ticker and form filters, then compare against a bounded filing search.
  • A webhook did not arrive: inspect signed delivery history and preserve its delivery id, status, attempt count, and request id.
  • Duplicate alert: deduplicate on the filing accession number and your delivery id.
  • Late alert: check the sweep cadence and source availability before changing the query.
Read Webhook and stream workflows for receiver behavior and Build a filing monitor for a signed handler.