Free Form 4 API
SEC Insider Data Guide

Free Form 4 API: the task behind the search

A developer searching for a free Form 4 API usually wants more than a list of filings. The practical goal is a stable SEC insider trading data API that turns EDGAR ownership documents into queryable records, supports ticker or CIK filters, and preserves enough provenance to audit every result.

The engineering challenge is lossless normalization. A filing can contain several reporting owners, relationship flags, non-derivative Table I rows, derivative Table II rows, holdings-only rows, transaction rows, numbered footnotes, joint-filing context, a trading-plan indicator, and an amendment to an earlier submission. A convenient JSON schema is useful only if those relationships remain reconstructable.

Choose between two operating models. A source-first pipeline retrieves SEC submission metadata and ownership XML, stores immutable files, and parses them locally. A normalized provider API reduces parsing and indexing work, and may add ticker search or webhooks, but must still expose accession, source URL, original values, filing version, and a clear contract for corrections.

SEC Form 4 filings API fields, codes, and amendments

A useful JSON API should retain issuer and reporting-owner CIKs, owner roles, form and amendment identity, earliest transaction and acceptance times, security table and title, transaction and deemed execution dates, code and voluntary indicator, shares, price, acquired-or-disposed state, direct or indirect ownership, nature of indirect ownership, post-transaction holdings, derivative terms, underlying security, footnotes, accession, and source URL.

What transaction codes P and S mean

Code P commonly identifies an open-market or private purchase, while S identifies a sale. Do not discard other codes or infer meaning from acquired/disposed alone: grants, exercises, gifts, conversions, expirations, tax-related dispositions, and transfers can change holdings without carrying the same interpretation. Preserve the source code and footnotes before deriving a display label.

Preserve Table I and Table II relationships

Table I describes non-derivative securities; Table II describes derivative securities and their underlying instruments. Keep exercise or conversion price, exercisable and expiration dates, derivative units, underlying title and amount, and post-transaction derivative holdings. Do not merge a derivative unit with its underlying common-share amount or count both as the same exposure.

Footnotes are part of the data model

Footnotes can explain weighted-average prices, price ranges, ownership through trusts or entities, vesting, conversion terms, tax withholding, or trading-plan context. Store footnotes once, retain row-to-footnote references, and expose them with the normalized transaction. Flattening footnote text into an unrelated filing note breaks auditability.

Interpret the Rule 10b5-1 checkbox precisely

Current Forms 4 and 5 ask whether a reported transaction was made under a contract, instruction, or written plan intended to satisfy the affirmative-defense conditions of Rule 10b5-1(c), together with the plan adoption date. Preserve the checkbox and adoption date as source fields. A checked box describes the filer’s stated plan context; it does not by itself prove that every legal condition was satisfied, make the transaction non-material, or turn a sale into a new discretionary bearish opinion.

How to handle Form 4/A amendments

Store the raw filing and accession, link each amendment to the original record, and apply corrections without silently overwriting history. Deduplicate at the transaction level so a corrected filing does not create a second trade.

How to evaluate a free insider trading API

Integrate a free Form 4 API with Python and JSON

Step 1: query SEC Form 4 data by ticker or CIK

Start with one company and a narrow date range. Confirm authentication, response status, pagination, sort order, timezone, latest filing date, and whether the response returns transactions or only filing headers.

Step 2: normalize Form 4 insider transactions JSON

Model filing, reporting owner, security, transaction row, holding row, derivative terms, footnote, and source version as related entities rather than one flat record. Keep raw XML or provider JSON for replay, preserve source text values, and derive typed numbers only with explicit null and unit rules.

Step 3: add Form 4 API webhook alerts safely

Verify webhook signatures, acknowledge quickly, process asynchronously, and make the consumer idempotent using an event ID or accession plus transaction identity. Reconcile webhook events against a periodic API pull.

Step 4: reconcile normalized output with source XML

For each fixture, compare reporting-owner count, Table I and II row counts, holdings-only rows, transaction rows, footnotes, amendments, and source hash. Include joint ownership, weighted prices, indirect holdings, derivatives, null prices, and multiple same-day transactions.

Step 5: version corrections without losing public history

Link Form 4/A to the original lineage, identify which owners, rows, holdings, or footnotes changed, and publish a deterministic current view. Keep the earlier public version for point-in-time research and emit a correction event for downstream consumers.

Step 6: measure webhook completeness and replay

Track SEC acceptance-to-delivery latency, duplicate rate, missed events, out-of-order amendments, retry attempts, and replay support. Periodic source reconciliation is required even when the webhook appears reliable.

Use QVeris to discover Form 4 data capabilities

FAQ

Authoritative references and next steps

Use the SEC EDGAR application programming interfaces, SEC Exchange Act Rules interpretations, and SEC privacy and security policy as sources for official access and field context. Provider documentation can explain a normalized schema, but it does not replace the original filing.