Automation recipe

SEC API for Zapier and Make

A self-serve HTTP recipe for automation builders who want to poll SEC filing changes and send matching records into a spreadsheet, CRM, Slack channel, or email workflow.

Subscribe on RapidAPI Try demo JSON View code examples

GET /v1/sec/changes?since=2026-07-01&form=8-K&limit=25

curl --request GET \
  --url "https://sec-event-intelligence.p.rapidapi.com/v1/sec/changes?since=2026-07-01&form=8-K&limit=25" \
  --header "x-rapidapi-host: sec-event-intelligence.p.rapidapi.com" \
  --header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"

Workflow Setup

This recipe validates whether buyers want SEC filing data inside automation tools before we build deeper app-specific support.

Create a scheduled automation that runs every hour or every business day.
Add an HTTP request step using the RapidAPI endpoint and key headers.
Filter the returned filings by ticker, form, or event type before writing to the next app.

Endpoints Used

The integration uses live SEC Event Intelligence endpoints available through RapidAPI subscriptions.

GET /v1/sec/changes
GET /v1/sec/watchlist/changes
GET /v1/sec/companies/search

Integration FAQ

Is this an official Zapier or Make app?

No. It is a standard HTTP API recipe that can be configured in automation tools with webhook or HTTP request steps.

What should the automation store?

Store the last successful since date or delivered accession numbers so the next run only handles new records.

No investment advice. These recipes move public SEC filing metadata into automation tools. They do not provide recommendations, ratings, signals, or personalized financial guidance.