SEC Filings API

Search, Stream, Extract & Convert SEC Filings Through One Unified API

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.

Real-Time + HistoricalSEC Filing Data
6Core SEC Data Tools
4Integration Protocols
~100 msReal-Time Filing Streaming Latency

What Data Will You Get?

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.

Historical SEC Filings

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.

Newly Published SEC Filings

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.

Original Filing Documents

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.

Extracted Filing Content

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).

Item-Level Filing Sections

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.

Full-Text Search Results

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.

XBRL Financial Data (JSON)

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.

Filing Content in Multiple Formats

Choose between plain text (type=text) or HTML (type=html) output when extracting filing content. This supports both machine processing and human-readable workflows.

Filing Discovery and Signals

Receive filing discovery events via WebSocket indicating when new filings become available, accompanied by historical backlog delivery immediately upon connection.

Global Coverage

Coverage

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.

DatasetCoverage
Historical FilingsSearch all SEC filing metadata using CIK, ticker, form types, filing dates, report dates, and items
Real-Time FilingsStream newly published SEC filings with approximately 100 ms latency post-EDGAR discovery
Supported Forms100% 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 ExtractionSupported 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 SearchCase-insensitive keyword and phrase search with inclusion/exclusion filters across filing documents
EDGAR DocumentsDirect stream download of original HTML, XML, XBRL, PDF, TXT, exhibits, and filing packages
XBRL DataConvert supported iXBRL/XBRL filings into structured JSON
Unique Capability

Intelligent SEC Filing Extraction Instead of Raw Documents

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.

AI Applications

Built for AI Applications with MCP

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.

SEC Filings MCP

json
{
  "mcpServers": {
    "FinFeedAPI-SEC": {
      "url": "https://api.sec.finfeedapi.com/mcp",
      "headers": {
        "X-APIKey": "YOUR_API_KEY_HERE"
      }
    }
  }
}
  • Hosted MCP server maintained and updated by FinFeedAPI
  • Dedicated X-APIKey header authentication
  • 6 self-describing tools discoverable through JSON Schema (filings_query, fulltext_search, extractor_extract_filing, extractor_extract_item, download_file, xbrl_convert)
  • Structured snake_case JSON responses
  • Native compatibility with Cursor, Claude Desktop, and MCP-enabled AI frameworks
Protocols & Interfaces

Multiple Access Protocols

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.

InterfaceAuthentication MethodBest For
REST APIHeader: Authorization: YOUR_API_KEYHistorical queries, full-text search, section extraction, raw downloads, and XBRL conversion
WebSocket APISocket auth handshakeStreaming newly published SEC filings (fillings events) with ~100 ms latency
JSON-RPC APIQuery: ?apikey=YOUR_API_KEYApplications preferring JSON-RPC 2.0 while accessing proxied REST endpoints
Hosted MCP ServerHeader: X-APIKey: YOUR_API_KEYAI agents, coding assistants, and LLM-powered financial research workflows
Platform Specifications

Engineering Standards

Built for production systems that depend on reliable financial data.

ISO 8601 UTC Timestamps

Output formatting strictly follows yyyy-MM-ddTHH:mm:ss.fffffffZ or yyyy-MM-dd. All time outputs are in UTC.

Consistent Data Model

Filing metadata, extraction endpoints, downloads, XBRL conversion, and streaming updates follow predictable response structures.

Snake Case Naming Conventions

Uniform snake_case naming across JSON properties, WebSocket payloads, and MCP tool schemas.

Unified API Key Access

One API key authenticates across REST, WebSocket, JSON-RPC, and MCP interfaces.

High-Precision Numeric Standard

Precision handling up to 19 digits overall (and up to 38 for aggregates) with up to 9 decimal places.

Official Open-Source SDKs

Ready-to-use libraries available on GitHub for Python, JavaScript, TypeScript, Go, C#, C++, Java, Ruby, PHP, Swift, .NET, R, Matlab, Haskell, and more.

Competitive Advantage

FinFeedAPI vs Direct Integrations

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.

FeatureDirect EDGAR IntegrationsFinFeedAPI SEC Filings API
AuthenticationMultiple tools and custom workflowsOne API key across every interface
Filing DiscoveryManual filtering and custom search logicStructured v1/filings Search API
Document SearchCustom indexing requiredBuilt-in v1/full-text Search
Filing ExtractionManual HTML parsingStructured Item Extraction (8-K, 10-K, 10-Q)
XBRL ProcessingCustom parsers and transformation pipelinesNative v1/xbrl-converter to JSON
Original DocumentsManual EDGAR downloadsDirect v1/download Stream Endpoint
Real-Time MonitoringPolling or custom infrastructureNative WebSocket Stream (wss://api.sec.finfeedapi.com)
Data NormalizationHeterogeneous text, XML, and HTML formatsPredictable snake_case JSON
AI CompatibilityCustom tool wrappers & prompt engineeringHosted MCP Server (/mcp)
Access MethodsVaries by implementationREST • WebSocket • JSON-RPC • MCP
Onboarding

Quickstart

Start integrating SEC filing data in just a few minutes.

  1. 1Create your free FinFeedAPI account.
  2. 2Generate an API key.
  3. 3Choose REST, WebSocket, JSON-RPC, or MCP.
  4. 4Search filings or subscribe to the real-time filing stream.
  5. 5Extract filing content, download documents, or convert XBRL into JSON.

Explore the documentation for endpoint examples, SDKs, authentication, supported filing types, and implementation guides.

REST API: Query Recent Apple Filings

bash
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.

REST API: Extract 8-K Item 1.01

bash
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"

REST API: Convert XBRL to JSON

bash
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.

The Challenge

SEC Filing Data Is More Than Document Downloads

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.

One Unified Developer Platform

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.

Use Cases

Common Applications

  • Regulatory monitoring platforms
  • Investment research systems
  • Financial analytics platforms
  • AI agents and LLM-powered research tools
  • Earnings and filing alert systems
  • Quantitative research
  • Compliance and risk monitoring
  • Corporate intelligence platforms
  • XBRL analytics pipelines
  • Financial data warehouses

Start Building

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.