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.

Run watchlist in RapidAPI Playground Download Python runner 5-minute quickstart Form 4 quickstart RapidAPI setup Preview demo JSON

GET /v1/sec/watchlist/changes

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 console
2. Open watchlistRun the watchlist endpoint in RapidAPI Playground
3. Use small parameterstickers=AAPL,MSFT,NVDA, since=2026-07-01, and limit=10
4. Confirm responseExpect HTTP 200 JSON with data and meta fields
5. 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 for AAPL,MSFT,NVDA polling
Company lookupRun company search in Playground before building issuer pages
Company filingsOpen RapidAPI for company filings, then use the company filings quickstart
Form 4 filingsOpen RapidAPI for Form 4 data, then use the Form 4 quickstart

Company filings first call

If the first workflow is issuer filing history, run the company filings endpoint in RapidAPI Playground, confirm HTTP 200 JSON, then reuse the same request in a company detail page, diligence queue, or scheduled refresh job.

Run company filings in RapidAPI Playground Open company filings quickstart Python client example

GET /v1/sec/company/AAPL/filings

curl --request GET \
  --url "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"

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.

Open Form 4 quickstart Review Form 4 use case

GET /v1/sec/insider-trades

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.

python3 sec_event_intelligence_first_call.py

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.py

Node.js first-call path

Use native fetch from Node.js, serverless functions, background jobs, or internal API routes. Keep the RapidAPI key in the server environment and call the RapidAPI host directly from trusted backend code.

Download JavaScript client Open JavaScript guide

node sec-first-call.mjs

const url = "https://sec-event-intelligence.p.rapidapi.com/v1/sec/watchlist/changes?tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=10";

const response = await fetch(url, {
  headers: {
    "x-rapidapi-host": "sec-event-intelligence.p.rapidapi.com",
    "x-rapidapi-key": process.env.RAPIDAPI_KEY
  }
});

if (!response.ok) {
  throw new Error(`SEC API request failed: ${response.status}`);
}

const payload = await response.json();
console.log(payload.meta);
console.log(payload.data?.length ?? 0);

If 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 elsewhere
Confirm selected appUse the app that is subscribed to SEC Event Intelligence, not a different RapidAPI project
Use RapidAPI hostRapidAPI requests go to sec-event-intelligence.p.rapidapi.com, not api.data-apis.com
Wait 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 polling
DashboardUse the dashboard example for internal filing review queues
PostmanImport the collection when the team wants a shared request workspace
PricingEstimate request volume before selecting a paid plan

Data infrastructure only. This first-call checklist uses public SEC filing metadata and does not provide investment advice, recommendations, ratings, or personalized financial guidance.