SEC Filings API

Form 4 insider trades, 13F institutional holdings, 8-K material events, and Form D funding rounds — pulled live from SEC EDGAR and returned as clean, typed JSON. Every endpoint resolves to a primary-source EDGAR filing; nothing here is scraped from a third-party aggregator.

This Actor works two ways:

1. Operation input — pick an operation from a dropdown (e.g. "13F: quarter-over-quarter position changes"), fill in a few fields, hit Start. The result lands in the run's dataset and in its OUTPUT key-value record, same as any other Actor. No need to touch Standby mode or write any code.
2. Standby API — if the Actor's Standby mode is enabled (see its Console page), it's instead a persistent REST API with ~25 endpoints you call directly over HTTP, with no run to start and no dataset to poll.

Both modes share the exact same route logic and return the exact same {error, data, message} JSON — pick whichever fits how you want to consume the data.

Why this one's different

Most "SEC filings" APIs wrap a single data type (usually just a bare filing list) and go stale. This one:

• Covers four filing types end-to-end (Form 3/4/5, 13F-HR, 8-K, Form D), not one.
• Actually parses the underlying XML (ownership documents, 13F info tables, Form D offering data) into clean fields, instead of just handing you an accession number to go fetch yourself.
• Ships analysis endpoints you won't find elsewhere: 13F quarter-over-quarter position changes (new/increased/decreased/sold-out positions, with % change), insider cluster-buy detection (multiple distinct insiders buying in the same window), and insider buy/sell sentiment summaries.
• Includes full-text search across all EDGAR filings since 2001.
• Bonus XBRL financials endpoint for raw fundamentals alongside the filings data.

Running with operation input

Every operation name mirrors one endpoint from the table below (e.g. thirteenf.changes → GET /v1/13f/:id/changes). Set operation, plus whichever of id / q / accession / limit / since / form / days / minInsiders / count / item / items / text / forms / startdt / enddt / ciks / tag / taxonomy that operation needs — the input schema's field descriptions say which fields apply to which operation. Unused fields are simply ignored.

Example input to get Berkshire Hathaway's latest 13F holdings:

{ "operation": "thirteenf.holdings", "id": "1067983" }

Example input for an insider-trading cluster-buy scan:

{ "operation": "insiders.clusterBuys", "id": "AAPL", "days": 30, "minInsiders": 2 }

The run's dataset gets exactly one record: the same {error, data, message} envelope the Standby API would return for that call. If error comes back true (bad ticker, missing filing, etc.) the run is marked Failed with the reason in its log — check the dataset/OUTPUT for the full body either way.

Calling the Standby API

This Actor's Standby URL is shown on its Console page (the "Standby" tab) — it looks like https://<actor-name>.<your-username>.apify.actor. Append any endpoint path from the table below to it, and authenticate with your Apify API token:

curl --request GET \
  --url 'https://sec-filings-api.your-username.apify.actor/v1/company/AAPL' \
  --header 'Authorization: Bearer YOUR_APIFY_TOKEN'

Or pass the token as a query parameter instead of a header:

https://sec-filings-api.your-username.apify.actor/v1/company/AAPL?token=YOUR_APIFY_TOKEN

Every example below omits the host and token for brevity — prepend your Standby URL and add your token to every call. Usage is billed the same way as any other Actor run on your Apify account (compute time while a request is in flight).

Response format

Every response, success or failure, has the same three top-level keys — check error before trusting data:

{ "error": false, "message": "Company profile for Apple Inc.", "data": { "...": "..." } }

{ "error": true, "message": "Unknown ticker \"NOTATICKER\"", "data": null }

• error — false on success, true on failure. Always a boolean, never missing.
• message — short human-readable summary. Safe to log or display as-is.
• data — the payload on success; always null on failure.

HTTP status codes are still meaningful (400 bad input, 404 not found, 429 rate-limited, 5xx upstream SEC failure) — the envelope doesn't replace them, it just makes the body predictable regardless of status.

Endpoints

All endpoints are under /v1. :id accepts either a ticker (AAPL) or a CIK (320193 / 0000320193), except where noted.

Company

Endpoint	Description
GET /v1/company/search?q=	Search companies by name or ticker
GET /v1/company/:id	Company profile (name, CIK, SIC, exchange, address, former names)
GET /v1/company/:id/filings?form=&limit=&since=	Raw filing history, any form type

Insider trades (Form 3/4/5)

Endpoint	Description
GET /v1/insiders/:id/trades?limit=&since=&form=	Parsed insider transactions for a company
GET /v1/insiders/:id/summary?days=90	Buy/sell share totals, estimated $ volume, buy/sell ratio, distinct insiders
GET /v1/insiders/:id/cluster-buys?days=30&minInsiders=2	Dates where multiple distinct insiders bought in the same window — an early signal most APIs don't surface
GET /v1/insiders/person/:cik	All ownership filings by a specific insider (their own CIK), across every company they report for
GET /v1/insiders/latest?count=40	Market-wide stream of the newest Form 4 filings

13F institutional holdings

Endpoint	Description
GET /v1/13f/search?q=	Find an institutional manager's CIK by name
GET /v1/13f/:id/holdings	Latest 13F-HR holdings, aggregated by CUSIP, with cover-page metadata
GET /v1/13f/:id/history?limit=20	Past 13F-HR filing periods on record
GET /v1/13f/:id/changes	Quarter-over-quarter diff: new positions, increased/decreased (with % change), sold-out, unchanged
GET /v1/13f/latest?count=40	Market-wide stream of the newest 13F-HR filings

8-K material events

Endpoint	Description
GET /v1/8k/:id?limit=&since=&item=	8-K filings for a company, with item codes decoded to plain English
GET /v1/8k/:id/:accession?text=true	Single filing: exhibit list + document URLs, optionally with extracted plain text
GET /v1/8k/latest?items=5.02,2.02&count=40	Market-wide stream, filterable by item code (e.g. 5.02 = exec changes, 2.02 = earnings)

Form D private offerings

Endpoint	Description
GET /v1/form-d/search?q=	Find an issuer's CIK by name
GET /v1/form-d/:id?limit=	Form D / D-A filings for an issuer
GET /v1/form-d/:id/:accession	Full parsed offering: amount raised, exemptions claimed, related persons, investor counts
GET /v1/form-d/latest?count=40	Market-wide stream of newly filed Form Ds (new funding rounds)

Full-text search & financials

Endpoint	Description
GET /v1/search/filings?q=&forms=&startdt=&enddt=&ciks=	Full-text search across all EDGAR filings since 2001
GET /v1/financials/:id/facts	All XBRL facts reported by the company
GET /v1/financials/:id/concept/:tag?taxonomy=us-gaap	One XBRL concept over time (e.g. Assets, Revenues)

Examples

Company profile by ticker

GET /v1/company/AAPL

{
  "error": false,
  "message": "Company profile for Apple Inc.",
  "data": { "cik": "0000320193", "name": "Apple Inc.", "tickers": ["AAPL"], "exchanges": ["Nasdaq"], "sic": "3571" }
}

Latest insider trades for a company

GET /v1/insiders/AAPL/trades?limit=1

{
  "error": false,
  "message": "Found 1 insider transaction filings for Apple Inc.",
  "data": {
    "cik": "0000320193",
    "trades": [{
      "reportingOwners": [{ "name": "Newstead Jennifer", "isOfficer": true, "officerTitle": "SVP, GC and Government Affairs" }],
      "nonDerivativeTransactions": [{ "transactionCode": "S", "transactionCodeLabel": "Open market or private sale", "shares": 2399, "pricePerShare": 343.36 }]
    }]
  }
}

Berkshire Hathaway's top 13F holdings

GET /v1/13f/1067983/holdings

{
  "error": false,
  "message": "Latest 13F-HR holdings for BERKSHIRE HATHAWAY INC (29 positions)",
  "data": {
    "holdings": [{ "cusip": "037833100", "nameOfIssuer": "APPLE INC", "shares": 227917808, "valueUsd": 65950296923 }]
  }
}

What changed in Berkshire's portfolio since last quarter

GET /v1/13f/1067983/changes

{
  "error": false,
  "data": {
    "summary": { "newPositions": 1, "increased": 7, "decreased": 6, "soldOut": 1, "unchanged": 15 },
    "newPositions": [{ "cusip": "23331A109", "nameOfIssuer": "D R HORTON INC", "shares": 3564 }]
  }
}

8-K filings market-wide, filtered to executive changes

GET /v1/8k/latest?items=5.02&count=5

A funding round's full details

GET /v1/form-d/2162748/0001315863-26-000760

{
  "error": false,
  "data": {
    "issuer": { "name": "Aliter Capital Annex, LP", "jurisdictionOfInc": "UNITED KINGDOM" },
    "offeringAmounts": { "totalOfferingAmount": "Indefinite", "totalAmountSold": 64006104 }
  }
}

Do

• Check error first, then read data. Don't infer failure from HTTP status alone — always read the body.
• Use a ticker (AAPL) or a CIK (320193) interchangeably for :id — whichever you have on hand.
• Use the search endpoints (/v1/company/search, /v1/13f/search, /v1/form-d/search) to resolve a company/institution/issuer name to a CIK before calling the other endpoints, if you don't already have a ticker or CIK.
• URL-encode query parameters, especially q= on /v1/search/filings when it contains quotes or spaces.
• Cache filing data on your side for anything keyed by an accession number — a filed document never changes, so there's no reason to re-fetch it.
• Treat cusip, cik, and accession numbers as strings, not numbers — they carry meaningful leading zeros (e.g. CUSIP 037833100, CIK 0000320193).

Don't

• Don't poll the /latest endpoints faster than once a minute. Filing feeds refresh on that cadence server-side, so hitting them more often just burns compute time for identical data.
• Don't treat this as a real-time market data feed. Filings show up on EDGAR on SEC's and the filer's own schedule (Form 4s within 2 business days of a trade, 13F-HR quarterly, etc.) — there's no live intraday component.
• Don't assume 13F valueUsd is in thousands. It's whole US dollars for periods after the SEC's 2023 rule change; only very old filings on record may still reflect the pre-2023 "thousands" convention as originally filed.
• Don't use this data as investment, legal, or compliance advice. It's raw, parsed filings data — not a recommendation engine.
• Don't assume every company has data for every endpoint. Most public companies never file a 13F (that's for institutional managers) or a Form D (that's for private offerings) — a 404 there is expected, not a bug.

Support

Questions, bug reports, or feature requests: Telegram @pintoflow.