# SRO Filings API Reference | SEC API > Complete API reference for the SEC SRO Filings Database API covering rule filings by self-regulatory organisations and the matching SEC rulemaking releases. Every request parameter, every searchable field and every response attribute, with types, constraints and a live example response. Source: https://sec-api.io/api-reference/sro-filings SEC enforcement and rulemaking POST`https://api.sec-api.io/sro` Search 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. [Read the guide for this API →](https://sec-api.io/docs/sro-filings-database-api) ## 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. ## Request body 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 | | `id` | Internal unique id of the SRO filing record. | ## Response 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. type: string Label of the document. The primary filing carries the releaseNumber as its type and is always present. Other labels include Exhibit 2, Exhibit 3, Exhibit 4, Exhibit 5, Submit a Comment on the file number, View Received Comments, Commission’s Request for Additional Information, Response to the Commission’s Request for Additional Information, and Order Granting Accelerated Approval of a Proposed Rule Change. url: string Direct URL of the document on sec.gov. Most are PDFs. Older filings can point to an HTML page instead. ## 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. | ## Request example POST https://api.sec-api.io/sro ```json { "query": "sro:NASDAQ", "from": "0", "size": "10", "sort": [{ "issueDate": { "order": "desc" } }] } ``` ```python from sec_api import SroFilingsApi sroFilingsApi = SroFilingsApi("YOUR_API_KEY") response = sroFilingsApi.get_data({ "query": "sro:NASDAQ", "from": "0", "size": "10", "sort": [{"issueDate": {"order": "desc"}}], }) ``` ```javascript import { sroFilingsApi } from "sec-api"; sroFilingsApi.setApiKey("YOUR_API_KEY"); const response = await sroFilingsApi.getData({ query: "sro:NASDAQ", from: "0", size: "10", sort: [{ issueDate: { order: "desc" } }], }); ``` ```bash curl -X POST https://api.sec-api.io/sro \ -H "Authorization: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "query": "sro:NASDAQ", "from": "0", "size": "10", "sort": [{ "issueDate": { "order": "desc" } }] }' ``` ## Response example 200 OK · application/json ```json { "total": { "value": 7963, "relation": "eq" }, "data": [ { "id": "dea4e1fa1371b4b91e08c7c3f5f42eae", "releaseNumber": "34-105132", "issueDate": "2026-03-31", "fileNumber": "SR-NYSEAMER-2026-25", "sro": "NYSE American LLC (NYSEAMER)", "details": "Notice of Filing and Immediate Effectiveness of a Proposed Rule Change to Modify the NYSE American Options Fee Schedule to Eliminate Certain Incentive Programs and Increase the Limit on the Maximum Combined Floor Broker Credits Paid on QCC Trades and...", "commentsDue": "21 days after publication in the Federal Register.", "urls": [ { "type": "34-105132", "url": "https://www.sec.gov/files/rules/sro/nyseamer/2026/34-105132.pdf" }, { "type": "Exhibit 5", "url": "https://www.sec.gov/files/rules/sro/nyseamer/2026/34-105132-ex5.pdf" }, { "type": "Submit a Comment on SR-NYSEAMER-2026-25", "url": "https://www.sec.gov/comments/sr-nyseamer-2026-25/notice-filing-immediate-effectiveness-proposed-rule-change-modify-nyse-american-options-fee-schedule" } ] } ] } ```