REST_API // AVAILABLE_ON_RAPIDAPI

PUT FORM 4 DATA
INSIDE YOUR PRODUCT.

Query normalized SEC Form 4 transactions and documented insider analytics through a production REST interface. Subscribe in RapidAPI, receive an application key and test the first request without operating the underlying ingestion pipeline.

View plans on RapidAPI Inspect the API contract

Operational queries

Retrieve recent activity by ticker, executive, date range or transaction size without loading the complete archive.

Derived analytics

Use windowed net flow, active-insider counts and directional leaders calculated under one documented methodology.

Research-ready JSON

Receive source lineage, quality state, normalized roles, issuer context, clusters and post-transaction outcomes.

Implementation quickstart

A server-side request is the integration boundary

The public customer credential is the RapidAPI application key. Send requests from a backend, serverless route, worker or scheduled job so that the key never reaches browser JavaScript.

Base URL: https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com
Host header: complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com
Auth header: x-rapidapi-key
Content type: application/json

Smallest possible request against the ticker transaction endpoint.

curl --request GET \
  --url 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/ticker/NVDA?limit=10' \
  --header 'x-rapidapi-host: complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com' \
  --header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY'

Customer authentication

RapidAPI supplies the customer key and host headers. Keep the key on a trusted server and proxy browser requests through your own backend. The provider proxy secret is infrastructure-only and is never a customer credential.

x-rapidapi-host: complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com
x-rapidapi-key: YOUR_RAPIDAPI_KEY

A clear division of responsibility

RapidAPI controls plan selection, billing, credentials and quota visibility.
InsiderAlpha controls endpoint behavior, data methodology and response semantics.
Your application controls end-user authorization, caching and key confidentiality.

Application fit

Designed for targeted, recurring access

Fintech applications

Power ticker pages, executive profiles and transaction-detail workflows with targeted responses.

Recurring research

Schedule monitored queries without repeatedly downloading and replacing a complete historical snapshot.

Internal data tools

Feed normalized transaction and analytics responses into notebooks, dashboards or review queues.

Endpoint catalog

8 production query surfaces

Full response contract

GET/api/v1/transactions/latest

Latest transactions

Returns the most recent publishable transactions across the covered universe, plus directional metrics for the returned batch.

Parameters

limitquery: integer · default 50 · 1–1000 — Maximum number of transactions returned.

Behavior notes

Rows are ordered by transaction date and internal identifier, descending.
Batch metrics describe only the rows returned, not the entire market.

Response shape

{
  "count": 50,
  "limit_applied": 50,
  "data": [{ "...": "TransactionOut" }],
  "batch_metrics": {
    "buy_volume": 1250000.0,
    "sell_volume": 830000.0,
    "net_flow": 420000.0
  }
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/latest?limit=50'

GET/api/v1/transactions/ticker/{symbol}

Transactions by ticker

Returns recent publishable Form 4 transactions for one normalized ticker symbol.

Parameters

symbolpathrequired: string — Case-insensitive U.S. equity ticker.
limitquery: integer · default 50 · 1–1000 — Maximum number of transactions returned.

Behavior notes

Returns HTTP 404 when the ticker has no publishable records.
Use the bulk dataset when complete history exceeds the API limit.

Response shape

{
  "count": 50,
  "limit_applied": 50,
  "data": [{ "...": "TransactionOut" }],
  "batch_metrics": null
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/ticker/TSLA?limit=50'

GET/api/v1/transactions/executive

Transactions by executive

Searches reporting-owner names and returns matching publishable transactions.

Parameters

namequeryrequired: string — Full name or whitespace-delimited name fragment as reported or normalized from SEC data.
limitquery: integer · default 50 · 1–1000 — Maximum number of transactions returned.

Behavior notes

This is a token-boundary name search, not probabilistic identity resolution.
Use reporting_owner_cik when a stable SEC identity is required.

Response shape

{
  "count": 12,
  "limit_applied": 50,
  "data": [{ "...": "TransactionOut" }],
  "batch_metrics": null
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/executive?name=Elon%20Musk&limit=50'

GET/api/v1/transactions/whales

Largest transactions

Returns the largest publishable transactions by effective nominal value inside a rolling calendar window.

Parameters

daysquery: integer · default 30 · 1–3650 — Rolling calendar-day lookback.
limitquery: integer · default 50 · 1–1000 — Maximum number of transactions returned.

Behavior notes

Effective value uses calculated_total_value when present and otherwise Total_Value.
Technical transactions are included; filter Type when interpreting directional activity.

Response shape

{
  "count": 50,
  "timeframe": "Last 30 days",
  "data": [{ "...": "TransactionOut" }]
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/whales?days=30&limit=50'

GET/api/v1/analytics/summary/{symbol}

Ticker transaction summary

Aggregates transaction count, shares and effective nominal value by SEC transaction code for one ticker.

Parameters

symbolpathrequired: string — Case-insensitive U.S. equity ticker.

Behavior notes

This endpoint groups all publishable history by transaction code.
Codes P and S represent open-market purchases and sales; other codes are not directional equivalents.

Response shape

{
  "ticker": "NVDA",
  "data": [
    {
      "Type": "S",
      "Total_Transactions": 24,
      "Total_Shares": 87500.0,
      "Total_Dollars": 10250000.0
    }
  ]
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/analytics/summary/NVDA'

GET/api/v1/analytics/snapshot/{symbol}

Windowed ticker analytics

Computes exact calendar-window activity, open-market flow, active insiders and directional leaders.

Parameters

symbolpathrequired: string — Case-insensitive U.S. equity ticker.
daysquery: integer · default 30 · 1–3650 — Inclusive calendar window. A 30-day request includes today and the preceding 29 dates.

Behavior notes

Net flow is code P value minus code S value.
Technical activity is reported separately and does not change directional net flow.

Response shape

{
  "ticker": "NVDA",
  "window_days": 30,
  "start_date": "2026-06-26",
  "end_date": "2026-07-25",
  "transaction_count": 8,
  "open_market_transaction_count": 3,
  "total_volume": 4100000.0,
  "buy_volume": 600000.0,
  "sell_volume": 3100000.0,
  "option_volume": 400000.0,
  "net_flow": -2500000.0,
  "active_insiders": 4,
  "latest_filing_date": "2026-07-23",
  "top_buyer": null,
  "top_seller": {
    "executive": "EXAMPLE EXECUTIVE",
    "position": "Officer",
    "transaction_type": "S",
    "total_value": 1500000.0,
    "transaction_count": 1
  }
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/analytics/snapshot/NVDA?days=30'

GET/api/v1/analytics/executive-snapshot

Executive analytics

Aggregates an executive's publishable activity and groups it by issuer.

Parameters

namequeryrequired: string · Minimum 2 characters — Executive or reporting-owner name.

Behavior notes

Total volume includes technical activity; buy and sell volume isolate codes P and S.
Company totals use effective nominal value.

Response shape

{
  "executive": "ELON MUSK",
  "transaction_count": 18,
  "total_volume": 7200000000.0,
  "buy_volume": 0.0,
  "sell_volume": 2400000.0,
  "net_flow": -2400000.0,
  "latest_filing_date": "2026-06-16",
  "companies": [
    {
      "ticker": "TSLA",
      "transaction_count": 18,
      "total_volume": 7200000000.0,
      "latest_filing_date": "2026-06-16"
    }
  ]
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/analytics/executive-snapshot?name=Elon%20Musk'

GET/api/v1/transactions/daterange

Transactions by date range

Returns publishable transactions whose transaction date falls inside an inclusive ISO-8601 date range.

Parameters

startqueryrequired: date — Inclusive start date in YYYY-MM-DD format.
endqueryrequired: date — Inclusive end date in YYYY-MM-DD format.
limitquery: integer · default 50 · 1–1000 — Maximum number of transactions returned.

Behavior notes

The range applies to transaction Date, not filing_date or accepted_at.
The current endpoint does not expose cursor pagination; use the bulk dataset for exhaustive extraction.

Response shape

{
  "count": 50,
  "start_date": "2026-03-01",
  "end_date": "2026-03-14",
  "data": [{ "...": "TransactionOut" }]
}

curl 'https://complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com/api/v1/transactions/daterange?start=2026-03-01&end=2026-03-14&limit=50'

Implementation patterns

Examples for real product workflows

These patterns use the backend's current response contract: targeted transaction lists, ticker analytics, executive snapshots and whale monitoring. They are intentionally server-side because RapidAPI keys should remain private.

Combine latest rows, a windowed snapshot and transaction-code totals for a ticker page.

type InsiderAlphaClientOptions = {
  key: string;
  host?: string;
};

async function getTickerProfile(symbol: string, options: InsiderAlphaClientOptions) {
  const host = options.host ?? "complete-s-p-500-insider-trading-dataset-sec-form-4.p.rapidapi.com";
  const ticker = encodeURIComponent(symbol.toUpperCase());
  const headers = {
    "x-rapidapi-host": host,
    "x-rapidapi-key": options.key,
  };

  const [transactions, snapshot, summary] = await Promise.all([
    fetch("https://" + host + "/api/v1/transactions/ticker/" + ticker + "?limit=25", { headers }),
    fetch("https://" + host + "/api/v1/analytics/snapshot/" + ticker + "?days=90", { headers }),
    fetch("https://" + host + "/api/v1/analytics/summary/" + ticker, { headers }),
  ]);

  for (const response of [transactions, snapshot, summary]) {
    if (!response.ok) throw new Error("InsiderAlpha API returned " + response.status);
  }

  return {
    transactions: await transactions.json(),
    snapshot: await snapshot.json(),
    summary: await summary.json(),
  };
}

Production checklist

Ship the integration like infrastructure, not a demo script

The API is useful inside applications when auth, caching, null handling and quota behavior are designed explicitly.

Keep keys server-side

Store x-rapidapi-key in environment variables and expose your own authenticated route to browsers or mobile apps.

Cache stable queries

Ticker summaries, snapshots and date ranges can usually be cached for minutes to reduce quota usage and latency.

Respect response bounds

limit defaults to 50 and is capped at 1,000. days is valid from 1 to 3,650. Use the bulk dataset for exhaustive history.

Handle empty and null fields

Some SEC lineage, metadata and return-enrichment fields are nullable, especially for historical or not-yet-matured rows.

Retry carefully

Apply short exponential backoff for 429 and 5xx responses, and surface 400, 404 and 422 as input or coverage states.

Separate data from advice

Net flow, cluster flags and returns are descriptive research fields. They should not be presented as recommendations.

Agent handoff

Integration instructions are available as Markdown

Use the repository note when another agent needs to wire the API into an app, notebook or backend service with the correct auth headers, endpoint constraints and response assumptions.

docs/api-agent-integration.md

Choose the API when…

• Your product needs current, targeted JSON responses.
• Users search by ticker, owner, window or transaction size.
• You prefer a recurring subscription and managed keys.
• Individual responses stay inside the documented page limit.

Choose the bulk dataset when…

• You need complete history beyond a targeted API response.
• You are backtesting, joining or training locally.
• You require a frozen, versioned research snapshot.
• DuckDB or Parquet scans are more economical for the job.

Bulk dataset · $99 one-time

Subscription questions

Before you subscribe

Where do I subscribe and see the current price?

Subscription takes place on the InsiderAlpha listing in RapidAPI. The plan shown there controls the current price, included quota, rate limits, renewal and any overage charges; this page deliberately does not duplicate values that can change in the marketplace.

Do I receive an API key from InsiderAlpha?

RapidAPI provides the application key used in the x-rapidapi-key header. Keep it on a trusted server. InsiderAlpha never asks customers to expose the provider-side RapidAPI proxy secret.

Is the API the same product as the complete dataset?

No. The API is designed for targeted JSON requests and individual application workflows. The complete dataset is a versioned bulk snapshot for exhaustive history, local joins and large research scans.

Can I use the API from browser JavaScript?

Do not place a RapidAPI key in public browser code. Route requests through your own backend or serverless function so the credential remains private and you can enforce your own authorization and caching.

How are quotas, billing and cancellation managed?

RapidAPI displays usage and billing in its developer dashboard. Review the selected plan before subscribing and monitor remaining quota there. Plan changes and cancellation are also managed through the RapidAPI account.

Does the API provide investment recommendations?

No. Responses contain reported transactions and documented derived analytics for research. Net flow, cluster flags and post-transaction outcomes are descriptive and do not establish causality or predict future performance.

Subscription ready

Confirm the live plan, then test one documented request

Review the marketplace terms before subscribing. Once RapidAPI provides your application key, use the endpoint catalog above or the full technical reference to begin the integration.

Read documentation View RapidAPI plans

Operational queries

Derived analytics

Research-ready JSON

A server-side request is the integration boundary

From marketplace plan to first response

Review the live plan

Subscribe in RapidAPI

Run a server-side request

Ready to inspect the active plan?

Customer authentication

A clear division of responsibility

Designed for targeted, recurring access

Fintech applications

Recurring research

Internal data tools

8 production query surfaces

Latest transactions

Parameters

Behavior notes

Transactions by ticker

Parameters

Behavior notes

Transactions by executive

Parameters

Behavior notes

Largest transactions

Parameters

Behavior notes

Ticker transaction summary

Parameters

Behavior notes

Windowed ticker analytics

Parameters

Behavior notes

Executive analytics

Parameters

Behavior notes

Transactions by date range

Parameters

Behavior notes

Examples for real product workflows

Ship the integration like infrastructure, not a demo script

Keep keys server-side

Cache stable queries

Respect response bounds

Handle empty and null fields

Retry carefully

Separate data from advice

Integration instructions are available as Markdown

Choose the API when…

Choose the bulk dataset when…

Before you subscribe

Confirm the live plan, then test one documented request