Skip to main content
Use Zapier to route SEC filing matches into an existing operating workflow. The reliable boundary is simple: SEC API delivers a signed monitor.match event; Zapier stores or routes the normalized filing fields; the next human or system can follow the source filing.

​
Set up the connection

  1. In Zapier, create a Zap with Webhooks by Zapier: Catch Hook and copy the HTTPS hook URL.
  2. In the signed-in SEC API dashboard, add that URL as an organization endpoint and subscribe it to monitor.match.
  3. Create the monitor in the same dashboard. A useful first monitor has a focused query, form filter, and a small ticker list.
Webhook and monitor configuration are human-authenticated organization actions. They require the dashboard’s WorkOS session; an API key cannot create, edit, test, or delete them.

​
Map a filing match

Use these fields in a Zapier action:
FieldUse it for
data.monitor.nameAlert and routing label
data.matches[].tickerCompany filter or destination key
data.matches[].formForm-specific logic
data.matches[].filingDateDeadline or recency logic
data.matches[].htmlUrlLink to the source filing
Use the dashboard’s test-delivery action to teach Zapier the payload. It sends webhook.test; real filing alerts send monitor.match on the scheduled monitor sweep.

​
Validate a configured monitor

curl -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/monitors/MONITOR_ID/matches?limit=10"
The API key is intentionally limited to these data reads. Keep the source URL with the Zapier row or task so reviewers can inspect the filing that caused the alert.