RapidAPI setup

SEC Event Intelligence on RapidAPI

Subscribe through RapidAPI for REST quotas, generated snippets, and marketplace-managed keys. Run the watchlist endpoint in RapidAPI Playground first, then move the generated snippet into dashboards, workers, or company filing pages.

Marketplace checkout Generated snippets Watchlist polling Company filings endpoint Free Basic tier
First RapidAPI request
curl "https://sec-event-intelligence.p.rapidapi.com/v1/sec/watchlist/changes?tickers=AAPL,MSFT&limit=25" \
  --header "x-rapidapi-host: sec-event-intelligence.p.rapidapi.com" \
  --header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"

Required headers

RapidAPI sends traffic to the SEC Event Intelligence REST API with two generated headers. Keep the key server-side for production apps and scheduled jobs.

Endpoint playground checklist

After subscribing, use RapidAPI Playground as the first live execution path. It confirms the selected app, key, host header, and endpoint parameters before the request is copied into an application.

Buyer-ready first endpoints

These endpoints cover the most common setup checks: a ticker watchlist feed, issuer-specific filing history, and company lookup before building a polling workflow.

Company filings request

Use this request when the app needs a company detail page, issuer filing timeline, compliance queue, or filing-history sync by ticker.

GET /v1/sec/company/AAPL/filings
curl "https://sec-event-intelligence.p.rapidapi.com/v1/sec/company/AAPL/filings?limit=25" \
  --header "x-rapidapi-host: sec-event-intelligence.p.rapidapi.com" \
  --header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"

Access route

RapidAPI is the self-serve REST route. Hosted MCP production tools use a direct Data APIs key only when an MCP client must call https://api.data-apis.com/mcp directly.

Troubleshooting

Most failed first calls come from missing RapidAPI headers, calling the Data APIs base URL with RapidAPI headers, or exposing the key in a browser-only app.