SEC Filing Data offers a website for researching filings and APIs for bringing filing information into applications. If you are looking for the best SEC filing API for your needs, start with the work you want to complete: identifying a company, finding a disclosure, reviewing a document, or turning supported filing content into structured data.
The API offering covers several distinct jobs, including company mapping, filing search, document retrieval, XBRL conversion, and specialized filing datasets. The sections below explain what each workflow helps you do, where coverage varies, and how pricing and license terms affect your intended use.
Use the website for filing research and review
The website brings together company search, filing lists, filing insights, and email alerts. It provides a starting point for users who want to find and read documents without building an integration.
On the search for SEC Filing Data, enter a company name, ticker, or CIK—the filer identifier used in SEC records—and select the matching company. Check the company identity before continuing, especially when a familiar brand differs from the legal filer name.
From the company’s filing list, narrow the results by form type. Open a filing using View, confirm it is the filing you need, then select the PDF option in the top-right corner to download it. The site also offers form-based discovery and Filing Insights for categories such as annual reports and IPOs. Its published search guide says an account is required.
Email alerts can help you follow filings through the website. Website email alerts are separate from programmatic streaming, which the current catalogue marks as planned. Likewise, finding words inside an opened filing is different from searching the contents of an entire filing database.
| API or service | What it does | Typical use |
|---|---|---|
| Website filing research | Browse filings and review documents online. | Read a company’s disclosures without an integration. |
| Mapping API | Connect identifiers with company details. | Confirm the company behind a ticker. |
| Query API | Find filing records and source references. | Build a list of relevant disclosures. |
| Extractor API | Pull selected text from supported filings. | Review a particular disclosure section. |
| XBRL conversion | Turn supported tagged financial content into JSON. | Bring reported figures into an analysis tool. |
| Document download/PDF generation | Retrieve supported source files or create PDFs. | Keep documents for review or archiving. |
| Specialized datasets | Provide focused company, ownership, offering, fund, subsidiary, and regulatory records. | Research a specific topic beyond general filing discovery. |
What the main API workflows help you do
An API becomes useful when you need to repeat a search, process documents, or connect results to an internal tool. SEC Filing Data’s documented workflows cover several stages of that process; choosing the right stage prevents unnecessary processing.
Match the API to the output you need: filing metadata, an original document, a generated PDF, an extracted section, or structured financial data. These outputs serve different purposes and should be evaluated separately.
Connect company identifiers with the Mapping API
Company mapping helps connect a known identifier, such as a ticker or CIK, with company details. Instead of manually resolving each company before searching its filings, an application can request a match and retain the confirmed identifiers.
The Mapping API’s documented examples return company names, CIKs, tickers, classifications, and addresses. A practical use is to confirm the company, save its CIK, and use that identifier in subsequent filing research. Review the returned identity before accepting a match; the reference describes daily updates but does not establish a complete history of every security or ticker.
Find relevant records with the Query API
The Query API searches filing metadata using supported company and filing attributes, including ticker, CIK, company name, form type, and accession number. It returns records describing matching filings, with available filer information, attachments, and source references.
For a dashboard that lists a company’s disclosures, this is the discovery step. Your application identifies the relevant filings, then decides which documents need to be opened or processed. A search result is not itself the full document, an extracted narrative section, or a set of financial statements.
Developers can retrieve results in batches rather than requesting the entire result set at once. Before relying on a particular search, confirm the supported filters and date behavior in the endpoint documentation.
Retrieve selected narrative sections
The Extractor API is intended for selected sections of supported 10-K, 10-Q, and 8-K filings. You identify the filing, its form type, and the item you want to retrieve. The documented response example contains filing identifiers and section text.
This can help a research application bring relevant disclosure text into a review or analysis workflow. Check how the returned sections are labeled: an item number can appear in more than one part of a filing. Confirm coverage for the forms and sections you need rather than assuming every document follows the same structure.
Convert supported XBRL content into financial data
XBRL conversion serves a different purpose from narrative extraction. It takes a supported filing or associated XBRL file and converts its tagged content into JSON that an application can process.
The converter’s documented outputs include income statements, balance sheets, cash flows, shareholders’ equity, and other reported items. This workflow may fit an application that needs financial information from filings rather than only a link to the report.
Evaluate conversion with representative filings and check the periods, units, and fields your application requires. Access to an older document does not establish that it contains convertible XBRL, and the reference has request-method inconsistencies that developers should resolve before integration.
Retrieve source documents or generate PDFs
The download service describes access to supported original filings and attachments, including HTML, XML, graphics, and text files. Original files can be useful for retaining source material or performing your own processing.
A generated PDF is a rendered copy for reading, review, or sharing. The reference’s worked examples describe submitting a filing URL, receiving generation information, and then downloading the resulting PDF. They do not fully clarify how to select original-file retrieval instead of PDF generation, so confirm the required download mode before building around it.
Specialized datasets for broader research
SEC Filing Data also publishes references for datasets beyond general filing discovery. These can support more focused research without requiring users to interpret every document manually:
- Company and subsidiary data: available filer contact details and Exhibit 21-derived subsidiary information can help connect companies, addresses, and corporate structures.
- Ownership data: insider transactions, parsed Forms 3, 4, and 5, and Form 144 records support research into reported ownership activity and restricted-sales filings.
- Offering and fund data: Form D records describe private offerings, while N-PORT data provides reported fund and portfolio information.
- Regulatory data: enforcement actions, administrative proceedings, litigation releases, accounting and auditing releases, and SRO filings support legal and regulatory research.
Use the SEC Filing Data API documentation to check the appropriate reference for searchable fields, response structure, history, and access requirements. Some regulatory databases document bulk JSON downloads, but a bulk metadata file should not be mistaken for an archive of all underlying documents. Enriched website and email information is offered as a paid add-on.
Related website and data services
Alongside API access, SEC Filing Data describes custom investor relations and corporate websites, filing widgets, and contact-data enrichment. Widgets are intended to display filings and disclosures on company websites; enrichment services describe customized delivery in Excel and API JSON formats.
These may be relevant when your goal is a public-facing filing display or a tailored dataset rather than a standalone API integration. Confirm the service scope and delivery arrangement separately. A service-page description does not establish that the work or dataset is included in a standard API subscription.
Coverage and history depend on the dataset
SEC Filing Data describes an overall filing archive reaching back to 1993 and support for more than 150 form types. That is platform-level scope, not a promise that every endpoint processes every form or supplies the same fields throughout that history.
For example, the Form D and Forms 3, 4, and 5 references state history from 2008, while section extraction names three supported form types. Company mapping, financial conversion, fund records, and regulatory datasets each need their own coverage check.
The public pages also differ on some archive figures and start dates. If a project depends on an early year, a particular issuer group, or a less common form, confirm that exact dataset and output before committing to it.
Availability matters as much as history. The current catalogue marks filing full-text search, WebSocket streaming, EDGAR index/archive APIs, and an MCP server as planned. Do not build a required production workflow around those features until availability is confirmed.
Pricing, eligibility, and licensing
The following public API prices were checked on October 19, 2026. The SEC Filing API pricing and licensing page separates evaluation, internal research, and Enterprise use.
| Plan | Published pricing | Intended use |
|---|---|---|
| Free | $0; 125 API calls | Internal research, product evaluation, and testing. |
| Research Internal Use | $45 monthly; $450 annually listed | Education, nonprofit, and government organizations; internal use. |
| Business Internal Use | $150 monthly; $1,500 annually listed | Businesses and for-profit organizations; internal use. |
| Enterprise | Contact sales | Commercial use and external publishing under the applicable agreement. |
Annual prices appear in the public page content, although the reviewed rendered view showed monthly cards. Confirm annual-plan availability before subscribing. Paid internal-use plans are subject to rate limits, but the public pricing page does not specify their numeric allowances.
For a customer-facing application, externally published data, or resale, confirm Enterprise licensing. Also check that the plan covers the datasets and add-ons you require. The Business Internal Use plan’s name should not be read as permission for external publication.
What developers should expect
How to use the SEC Filing Data API describes creating an account, generating an API key, maintaining an active subscription, and using the sandbox to explore supported requests. The free allowance gives prospective users a way to evaluate the product without establishing unrestricted access to every capability.
The references provide parameter tables, request examples in multiple languages, status codes, and some sample responses. That material can help a developer understand the integration, but parts of the documentation need clarification. Authentication examples, request methods, and some snippets are not fully consistent.
Use the individual endpoint reference as the starting point and resolve any conflicting instructions before depending on a workflow. Then check actual results through your authorized access: whether the right records are found, whether the required content is returned, and whether the application handles missing data, pagination, and errors.
A useful evaluation can stay small. Choose a recent filing, an older filing, and an example relevant to your specialized data needs. Follow each from discovery to the required output, then confirm the expected request volume, coverage, and permitted use. This article is based on public documentation; it does not report an authenticated end-to-end API test.
Assess the fit for your project
SEC Filing Data offers a path from manual filing research to repeatable discovery and supported document processing. Its value for your project depends on which steps it can handle with the coverage, outputs, and usage rights you need.
When deciding what makes the best SEC filing API for your workflow, start with one concrete task. Confirm that SEC Filing Data can complete it using currently documented features, then evaluate the subscription and any remaining integration work before expanding the scope.
