SEC enforcement and rulemaking
SRO Filings
https://api.sec-api.io/sroSearch every SRO-related filing and the SEC rulemaking release that goes with it, such as notices, orders and requests for comments. The database covers all SROs supervised by the SEC and holds more than 30,000 documents from 1995 to present, updated daily.
Authentication
Send the API key either as a header or as a query parameter. The header is preferred; the query parameter exists for cases where a header cannot be set, such as opening a URL directly in a browser.
Authorization: required header
The API key on its own. Do not prefix it with Bearer or any other word.
Example Authorization: YOUR_API_KEY
token: optional query parameter
The API key, appended to the URL. Use this only when a header is not possible.
A JSON object. Content-Type must be application/json.
query: required string
The search expression in Lucene syntax, written as field:value. Every field listed under Searchable fields can be used, combined with AND, OR, NOT, ranges and wildcards.
Example sro:NASDAQ
from: string, Maximum 10000
Index of the first result to return, used for pagination. Increment by the value of size to page through results.
Default "0"
size: string, Maximum 50
Number of SRO filings to return in one response.
Default "50"
sort: array of object
Sort order. Each item maps one field to an order object, for example [{ "issueDate": { "order": "desc" } }].
Default [{ "issueDate": { "order": "desc" } }]
order: string
Either asc or desc.
Searchable fields
Every field below can be used inside query. 9 fields are searchable, and they match the structure of the objects returned in the response.
| Field | Description |
|---|---|
releaseNumber | Release number associated with the filing, e.g. "34-98702" |
issueDate | Release date of the filing (YYYY-MM-DD) |
fileNumber | File number of the filing, e.g. "SR-ISE-2023-22" |
sro | SRO associated with the filing, e.g. "Nasdaq ISE, LLC (ISE)" |
details | Free-text description of the filing / rulemaking action |
commentsDue | Date by which comments on the filing are due |
urls.type | Document type label (release number, "Exhibit 5", "Submit a Comment on …", etc.) |
urls.url | Direct URL to the SEC-hosted document or comment page |
A JSON object. Nested attributes are collapsed; expand one to see its fields.
total: object
How many SRO filings matched the query.
value: integer
Number of matching SRO filings.
relation: string
Either eq, meaning value is exact, or gte, meaning value is a floor.
data: array of object
The matching SRO filings, at most size per response. Each object holds the metadata of one SRO filing and the SEC rulemaking release that goes with it.
id: string
Internal unique id of the SRO filing record.
releaseNumber: string
Release number associated with the filing, for example 34-98702.
issueDate: string
Release date of the filing, YYYY-MM-DD.
fileNumber: string
File number of the filing, for example SR-ISE-2023-22.
sro: string
The SRO associated with the filing, for example Nasdaq ISE, LLC (ISE).
details: string
Description of the filing, for example Notice of Filing and Immediate Effectiveness of Proposed Rule Change to Amend its Complex Order Rules.
commentsDue: optional string
Date by which comments on the filing are due, for example 21 days after date of publication in the Federal Register. Null when the release invites no comments.
urls: array of object
Every SEC-hosted document attached to the filing: the primary release, its exhibits, and the comment pages.
Status codes
200 | Success. The response holds total and data. |
400 | The request body could not be parsed, or the Lucene expression in query is malformed. |
403 | The API key is missing, or it is not valid. |
429 | Too many requests. Slow the request rate and retry. |
500 | Server error. Retry, and report it if it persists. |