Structured delivery
Designed for API requests, local files and repeatable research workflows.
SEC Form 4 API
SEC Form 4 API for insider transaction products
Build ticker pages, research dashboards and monitoring workflows with normalized SEC Form 4 transaction data delivered as JSON through RapidAPI.
Built for developers who need structured Form 4 data without maintaining an EDGAR ingestion pipeline.
Documented contract
Field definitions, endpoint behavior and data limitations are explicit.
Commercial path
Move from sample or docs into API access, dataset purchase or direct contact.
What the API returns
The API exposes targeted JSON endpoints for current transactions and derived analytics. It is optimized for product surfaces where users search by ticker, executive, window, date range or transaction size.
- Latest transactions with batch buy, sell and net-flow metrics.
- Ticker and executive transaction searches with normalized response fields.
- Windowed analytics for net flow, active insiders and directional leaders.
- Whale and date-range routes for monitoring and review queues.
Why it is useful
A Form 4 API should reduce integration work, not just expose raw filings. InsiderAlpha keeps the response contract focused on queryable rows, SEC lineage and research fields that a frontend or backend can use directly.
- No need to operate SEC polling, parsing, reconciliation or response shaping.
- Consistent field names across transaction and analytics endpoints.
- Server-side authentication model using RapidAPI customer credentials.
- Commercial path to the bulk dataset when complete history is needed.
Buyer workflow
From search intent to implementation
This page is built to route high-intent traffic toward the most appropriate commercial next step: API subscription, dataset sample, full release or technical documentation.
- 01
Subscribe or review the current plan on RapidAPI.
- 02
Store the RapidAPI key in a backend or serverless environment.
- 03
Start with `/api/v1/transactions/ticker/{symbol}` or `/api/v1/analytics/snapshot/{symbol}`.
- 04
Cache stable responses and route browser requests through your own backend.
Common questions
Is this a public browser API?
No. Customer credentials come from RapidAPI and should stay server-side. Browser and mobile apps should call your own backend route.
Does the API include investment recommendations?
No. Responses contain reported Form 4 transactions and descriptive analytics. They should not be presented as buy, sell or hold recommendations.
Commercial next step
Turn this search into a working data workflow
Start with the path that matches the job: API access for targeted application calls, or the versioned dataset for local research and full-history analysis.