RapidAPI first call
Run the first SEC API call
Use one watchlist request to confirm the subscribed RapidAPI app, generated key, host header, endpoint parameters, and JSON response before copying code into a backend, worker, or dashboard.
curl --request GET \
--url "https://sec-event-intelligence.p.rapidapi.com/v1/sec/watchlist/changes?tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=10" \
--header "x-rapidapi-host: sec-event-intelligence.p.rapidapi.com" \
--header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"First-call checklist
Start inside RapidAPI Playground so the selected app, subscription plan, generated headers, and endpoint URL are all handled in one place before the request is moved to production code.
1. Subscribe or select appUse the active RapidAPI app for SEC Event Intelligence before opening the endpoint console2. Open watchlistRun the watchlist endpoint in RapidAPI Playground3. Use small parameterstickers=AAPL,MSFT,NVDA,since=2026-07-01, andlimit=104. Confirm responseExpect HTTP 200 JSON withdataandmetafields5. Copy server-side snippetMove the generated code into a backend, worker, cron job, or serverless function
Choose the first paid workflow
Pick the smallest workflow that proves the buyer's use case, then run that endpoint through RapidAPI before adding storage, alerts, or dashboards.
Watchlist alertsRun the watchlist playground forAAPL,MSFT,NVDApollingCompany lookupRun company search in Playground before building issuer pagesCompany filingsOpen RapidAPI for company filings, then use the company filings quickstartForm 4 filingsOpen RapidAPI for Form 4 data, then use the Form 4 quickstart
Form 4 first call
If the first workflow is insider filing metadata, use the Form 4 quickstart. It calls the live insider-filings endpoint with a small ticker-scoped request and keeps the same RapidAPI headers.
curl --request GET \
--url "https://sec-event-intelligence.p.rapidapi.com/v1/sec/insider-trades?ticker=MSFT&limit=25" \
--header "x-rapidapi-host: sec-event-intelligence.p.rapidapi.com" \
--header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"Server-side first-call runner
Use the runner when the first call should happen from a terminal,
worker, or serverless environment instead of a browser. It reads
RAPIDAPI_KEY from the environment, calls the
watchlist endpoint, and prints the response metadata and filing
counts.
curl -L "https://api.data-apis.com/downloads/sec-event-intelligence-first-call.py" \
-o sec_event_intelligence_first_call.py
RAPIDAPI_KEY="YOUR_RAPIDAPI_KEY" \
python3 sec_event_intelligence_first_call.pyIf RapidAPI usage still shows zero
A subscription alone does not create API traffic. RapidAPI usage starts after the endpoint is executed through the subscribed app or from server-side code using the generated RapidAPI headers.
Run in Playground firstExecute the watchlist request from the RapidAPI endpoint console before copying snippets elsewhereConfirm selected appUse the app that is subscribed to SEC Event Intelligence, not a different RapidAPI projectUse RapidAPI hostRapidAPI requests go tosec-event-intelligence.p.rapidapi.com, notapi.data-apis.comWait for analyticsRapidAPI charts can lag the request by a few minutes after a successful call
Next production step
After the first HTTP 200 response, keep the RapidAPI key out of browser code and run the request from a backend path that can schedule polling, store last-seen accession numbers, and send alerts only when new filings arrive.
WorkerUse the alert worker example for scheduled watchlist pollingDashboardUse the dashboard example for internal filing review queuesPostmanImport the collection when the team wants a shared request workspacePricingEstimate request volume before selecting a paid plan