SecBlast v3 API
SEC EDGAR filings over a plain REST API.
Filings, their documents and the entities that file them, as read-only JSON under api.secblast.com/v3. Each record carries the accession number of the filing it came from.
Early release. The dataset is still being loaded and today covers a limited window of recent filings, not the whole EDGAR archive. The explorer shows what is there now.
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.secblast.com/v3/filings"YOUR_API_KEY stands for an API key. A key can also be sent in the X-API-Key header or as ?api_key=.
What makes v3 different
Tied to the source filing
Every filing record carries its SEC accession number, and its documents are the files as they were filed.
Uncapped cursor pagination
Filing lists page with a keyset cursor. There is no page-count ceiling: follow the cursor until the list ends.
Documents, byte for byte
Filing documents are served exactly as filed, with ETag and Range support for caching and partial downloads.
The API today
Twelve read-only GET routes. Errors are RFC 9457 problem bodies with a code and a request_id; unknown parameters are rejected instead of being ignored.
| Route | Returns | Key |
|---|---|---|
| /v3/filings | Filings, with 16 filters and a keyset cursor | Required |
| /v3/filings/{accession} | One filing | Required |
| /v3/filings/{accession}/documents | The documents of a filing | Required |
| /v3/filings/{accession}/documents/{seq-or-filename} | A document's raw bytes (ETag, Range) | Required |
| /v3/filings/{accession}/events | The events of a filing | Required |
| /v3/filings/{accession}/header | The filing header | Required |
| /v3/entities | Entities | Required |
| /v3/entities/{cik} | One entity | Required |
| /v3/forms | Form types | Required |
| /v3/coverage | What the API currently covers | Required |
| /v3/openapi.json | The OpenAPI description | Not needed |
| /v3/health | Service health | Not needed |
The full description is the OpenAPI file; the explorer lets you browse the data in a browser and shows what the API covers at the moment.
Start on the Free plan
Sign in with an email code, Google or GitHub. Your first API key is created at sign-up; no card is needed.