First request chooser
Choose the smallest request that matches the integration path.
REST buyers should start in RapidAPI. MCP clients can run a
no-key tools/call before sending production
credentials.
Buyer setup path
Use the route that matches the client before choosing a paid
plan. REST integrations should use RapidAPI checkout. Hosted
MCP clients should run public setup calls first, then request a
direct key only for production tools/call data.
RapidAPI setup checklist
After subscribing, copy the generated key from the RapidAPI
console and send both RapidAPI headers with every protected
endpoint request.
x-rapidapi-hostsec-event-intelligence.p.rapidapi.com
x-rapidapi-keyYour generated RapidAPI application key
First requestRun it in RapidAPI Playground with GET /v1/sec/watchlist/changes?tickers=AAPL,MSFT&limit=25
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"
Python first request
import requests
headers = {
"x-rapidapi-host": "sec-event-intelligence.p.rapidapi.com",
"x-rapidapi-key": "YOUR_RAPIDAPI_KEY",
}
response = requests.get(
"https://sec-event-intelligence.p.rapidapi.com/v1/sec/watchlist/changes",
headers=headers,
params={"tickers": "AAPL,MSFT", "limit": "25"},
timeout=30,
)
response.raise_for_status()
print(response.json())
JavaScript first request
const response = await fetch(
"https://sec-event-intelligence.p.rapidapi.com/v1/sec/watchlist/changes?tickers=AAPL,MSFT&limit=25",
{
headers: {
"x-rapidapi-host": "sec-event-intelligence.p.rapidapi.com",
"x-rapidapi-key": "YOUR_RAPIDAPI_KEY"
}
}
);
if (!response.ok) throw new Error(`SEC API request failed: ${response.status}`);
console.log(await response.json());
MCP no-key first call
These public JSON-RPC requests are safe setup checks for
remote MCP clients. The demo call verifies live sample data,
and the subscription-info call returns the REST checkout,
hosted MCP access, pricing, and client-config links.
tools/call sec_demo_latest_filings
curl -sS https://api.data-apis.com/mcp \
-H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","id":"demo-latest-filings","method":"tools/call","params":{"name":"sec_demo_latest_filings","arguments":{"limit":3}}}'
tools/call sec_subscription_info
curl -sS https://api.data-apis.com/mcp \
-H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","id":"subscription-info","method":"tools/call","params":{"name":"sec_subscription_info","arguments":{}}}'
Latest filings
Fetch recent filings and optionally filter by SEC form type.
GET /v1/sec/latest?form=8-K&limit=50
Change feed
Poll for newly observed filings and material event changes since a date.
GET /v1/sec/changes?since=2026-07-01&ticker=AAPL&limit=50
Watchlist changes
Poll multiple tickers in one request and receive changes grouped by ticker.
GET /v1/sec/watchlist/changes?tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=25
Company search
Resolve ticker symbols, CIKs, and company names before calling filing feeds.
GET /v1/sec/companies/search?q=apple&limit=10
GET /v1/sec/company/AAPL/profile
Demo JSON
Preview response shape and current coverage before subscribing.
curl https://api.data-apis.com/demo
Company feed
Use a ticker symbol or 10-digit CIK for company-specific feeds.
GET /v1/sec/company/AAPL/filings?limit=25
GET /v1/sec/company/AAPL/events?limit=25
Insider trades
Retrieve Forms 3, 4, and 5, optionally scoped to one company.
GET /v1/sec/insider-trades?ticker=MSFT&limit=25
Filing summary
Resolve a filing by accession number and receive normalized metadata.
GET /v1/sec/forms/0001214659-26-008121/summary
Monitoring
Use health and stats endpoints to check freshness and coverage.
GET https://api.data-apis.com/health
GET /v1/sec/stats