SEC Filing Metadata
Retrieve structured metadata for SEC filings, including accession number, form type, filing date, report date, company name, CIK, and document size. Metadata can be filtered, sorted, and paginated through the filings endpoint.
Access historical SEC filings, real-time filing notifications, full-text search, structured filing extraction, XBRL conversion, and original EDGAR documents through one standardized developer API.
FinFeedAPI provides unified access to SEC filing data through REST, WebSocket, JSON-RPC, and hosted Model Context Protocol (MCP). Instead of building separate integrations for filing discovery, document search, XBRL processing, and real-time monitoring, developers work with one consistent platform designed for financial applications, AI systems, research platforms, compliance workflows, and investment analytics.
Retrieve structured metadata for SEC filings, including accession number, form type, filing date, report date, company name, CIK, and document size. Metadata can be filtered, sorted, and paginated through the filings endpoint.
Access historical filings from the EDGAR archive, covering all SEC forms (such as 10-K, 10-Q, 8-K, S-1, S-3, 20-F, 40-F, and other filing types). Filings can be queried by CIK, ticker, form type, and date range.
Receive a real-time stream of newly published SEC filings through the WebSocket API. New filings are delivered shortly after they appear in EDGAR with an average broadcast latency of ~100 ms.
Download original filing documents directly from the SEC EDGAR archive. Supported file types include HTML, XML, XBRL, TXT, PDF, and other formats submitted to the SEC.
Retrieve classified text or HTML content from SEC filings using the extractor endpoint. Content is structured based on the form type (supported for 8-K, 10-K, and 10-Q).
Extract specific items or sections from 8-K, 10-K, and 10-Q filings (e.g., Item 1.01 for 8-K, or Item 1 / PartI 1 for 10-K/10-Q). Item-based extraction allows direct access to targeted disclosures without processing full documents.
Search across SEC filing documents using keyword-based full-text search. Results can be filtered by form type, filing date range, and inclusion (text_contains) or exclusion (text_not_contain) of specific terms.
Convert XBRL filings into structured JSON output, including financial statements (Income Statement, Balance Sheet, Cash Flow), accounting policies, and cover page metadata. Supported inputs include accession numbers, HTML URLs, and XBRL file URLs.
Choose between plain text (type=text) or HTML (type=html) output when extracting filing content. This supports both machine processing and human-readable workflows.
Receive filing discovery events via WebSocket indicating when new filings become available, accompanied by historical backlog delivery immediately upon connection.
The SEC Filings API provides unified access to filing discovery, document retrieval, structured extraction, real-time monitoring, and XBRL conversion through one consistent developer platform.
| Dataset | Coverage |
|---|---|
| Historical Filings | Search all SEC filing metadata using CIK, ticker, form types, filing dates, report dates, and items |
| Real-Time Filings | Stream newly published SEC filings with approximately 100 ms latency post-EDGAR discovery |
| Supported Forms | 100% SEC Form Coverage (8-K, 10-K, 10-Q, S-1, S-3, 20-F, 40-F, Form 4, 13F, Form D, ADV, etc.) |
| Item-Level Extraction | Supported for 8-K, 10-K, and 10-Q (e.g., 8-K: 1.01, 2.01; 10-K/10-Q: 1, 2, PartI 1) |
| Full-Text Search | Case-insensitive keyword and phrase search with inclusion/exclusion filters across filing documents |
| EDGAR Documents | Direct stream download of original HTML, XML, XBRL, PDF, TXT, exhibits, and filing packages |
| XBRL Data | Convert supported iXBRL/XBRL filings into structured JSON |
Most SEC APIs stop at returning filing metadata or downloading original EDGAR documents.
FinFeedAPI goes several steps further by transforming complex regulatory filings into structured, developer-friendly datasets.
Instead of building custom parsers for thousands of HTML documents, developers can retrieve classified filing content, extract individual filing items, perform full-text searches across filings, convert XBRL into structured JSON, or download original source files—all through the same API infrastructure.
Whether you need Item 1.01 from an 8-K, complete 10-K filings for LLM training, or normalized financial statements from XBRL, every workflow is available through one standardized platform.
The SEC Filings API is available through a hosted Model Context Protocol (MCP) server, allowing AI assistants, coding agents, and autonomous applications to interact with SEC filings through standardized tool calls. Instead of building custom REST integrations, parsing documentation, or maintaining intermediary services, AI applications automatically discover available tools through JSON Schema. Large Language Models can query filings, search document text, extract filing sections, download EDGAR files, and convert XBRL into JSON using structured, self-describing interfaces.
{
"mcpServers": {
"FinFeedAPI-SEC": {
"url": "https://api.sec.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "YOUR_API_KEY_HERE"
}
}
}
}Choose the interface that best matches your application architecture. All interfaces expose the same standardized SEC filing datasets while using consistent ISO 8601 UTC timestamps and predictable response schemas.
| Interface | Authentication Method | Best For |
|---|---|---|
| REST API | Header: Authorization: YOUR_API_KEY | Historical queries, full-text search, section extraction, raw downloads, and XBRL conversion |
| WebSocket API | Socket auth handshake | Streaming newly published SEC filings (fillings events) with ~100 ms latency |
| JSON-RPC API | Query: ?apikey=YOUR_API_KEY | Applications preferring JSON-RPC 2.0 while accessing proxied REST endpoints |
| Hosted MCP Server | Header: X-APIKey: YOUR_API_KEY | AI agents, coding assistants, and LLM-powered financial research workflows |
Built for production systems that depend on reliable financial data.
Output formatting strictly follows yyyy-MM-ddTHH:mm:ss.fffffffZ or yyyy-MM-dd. All time outputs are in UTC.
Filing metadata, extraction endpoints, downloads, XBRL conversion, and streaming updates follow predictable response structures.
Uniform snake_case naming across JSON properties, WebSocket payloads, and MCP tool schemas.
One API key authenticates across REST, WebSocket, JSON-RPC, and MCP interfaces.
Precision handling up to 19 digits overall (and up to 38 for aggregates) with up to 9 decimal places.
Ready-to-use libraries available on GitHub for Python, JavaScript, TypeScript, Go, C#, C++, Java, Ruby, PHP, Swift, .NET, R, Matlab, Haskell, and more.
Working directly with SEC filings often means combining multiple tools for discovery, document retrieval, parsing, search, XBRL processing, and real-time monitoring. FinFeedAPI unifies these capabilities behind one standardized developer platform.
| Feature | Direct EDGAR Integrations | FinFeedAPI SEC Filings API |
|---|---|---|
| Authentication | Multiple tools and custom workflows | One API key across every interface |
| Filing Discovery | Manual filtering and custom search logic | Structured v1/filings Search API |
| Document Search | Custom indexing required | Built-in v1/full-text Search |
| Filing Extraction | Manual HTML parsing | Structured Item Extraction (8-K, 10-K, 10-Q) |
| XBRL Processing | Custom parsers and transformation pipelines | Native v1/xbrl-converter to JSON |
| Original Documents | Manual EDGAR downloads | Direct v1/download Stream Endpoint |
| Real-Time Monitoring | Polling or custom infrastructure | Native WebSocket Stream (wss://api.sec.finfeedapi.com) |
| Data Normalization | Heterogeneous text, XML, and HTML formats | Predictable snake_case JSON |
| AI Compatibility | Custom tool wrappers & prompt engineering | Hosted MCP Server (/mcp) |
| Access Methods | Varies by implementation | REST • WebSocket • JSON-RPC • MCP |
Start integrating SEC filing data in just a few minutes.
Explore the documentation for endpoint examples, SDKs, authentication, supported filing types, and implementation guides.
curl -X GET "https://api.sec.finfeedapi.com/v1/filings?ticker=AAPL&form_type=10-K,10-Q&filling_date_start=2025-01-01&page_size=10" \
-H "Authorization: YOUR_API_KEY"API query filters for filing dates use the schema parameter names filling_date_start and filling_date_end.
curl -X GET "https://api.sec.finfeedapi.com/v1/extractor/item?accession_number=0000320193-25-000073&item_number=1.01&type=text" \
-H "Authorization: YOUR_API_KEY"curl -X GET "https://api.sec.finfeedapi.com/v1/xbrl-converter?accession-no=0001564590-21-004599" \
-H "Authorization: YOUR_API_KEY"The API returns standardized filing metadata with consistent JSON structures, ISO 8601 UTC timestamps, accession numbers, filing dates, report dates, and document information.
Building production financial software around SEC filings involves much more than fetching raw HTML files from EDGAR.
Developers often need to search filings by company or keyword, monitor new submissions in real time, parse out specific filing items, standardize XBRL accounting taxonomies, download associated exhibits, and clean disparate formatting before the underlying data becomes actionable.
Maintaining separate, uncoordinated pipelines for discovery, section parsing, search, streaming, and file storage quickly creates unnecessary engineering overhead.
FinFeedAPI addresses this by bringing every stage of the SEC filing lifecycle into a unified developer platform backed by standardized APIs, single-key authentication, predictable schemas, comprehensive SDKs, and native AI integration via MCP.
Access historical SEC filings, real-time filing notifications, full-text search, structured extraction, XBRL conversion, and original EDGAR documents through one developer platform.
If you're building investment research tools, compliance systems, AI-powered financial applications, regulatory monitoring platforms, or document processing pipelines, FinFeedAPI provides one standardized interface for the complete SEC filing workflow.