Extracted Filing Content

Extracted Filing Content

Extract structured text or HTML content from SEC filings through the FinFeedAPI SEC Filings API.

Instead of downloading and parsing complete filing documents, applications can retrieve the entire filing content or specific filing items from supported forms. This simplifies access to commonly used sections of SEC filings while reducing the amount of custom document processing required.

What Is Extracted Filing Content?

SEC filings often contain lengthy documents with multiple sections covering financial results, business operations, risk disclosures, management discussion, exhibits, and other regulatory information.

Classified items from supported forms

For supported filing forms (8-K, 10-K, and 10-Q) the Extracted Filing Content endpoints classify filing documents into structured items. Applications can retrieve either the complete filing content or a specific filing item without manually parsing the original document.

Plain text or HTML output

Content can be returned as plain text or HTML, making it suitable for analytics platforms, search systems, AI applications, compliance workflows, and financial research.

Why Extract Filing Content?

Many applications need specific information from regulatory filings rather than the original filing document.

Skip custom document parsing

Retrieving structured filing content helps applications:

  • extract individual sections from supported filings
  • retrieve complete filing content as text or HTML
  • build AI and RAG pipelines from regulatory documents
  • analyze disclosures without custom document parsing
  • index filing content for search
  • automate regulatory research workflows
  • monitor specific disclosure sections
  • process filings more efficiently than parsing raw documents

How Filing Extraction Works

Applications can retrieve either the complete extracted filing content or a specific filing item. The complete filing endpoint requires the filing accession number, while item-level extraction additionally requires the filing item number.

Complete filing content

  1. 1Find the filing
  2. 2Retrieve the accession number
  3. 3Extract the complete filing
  4. 4Receive text or HTML

Use GET /v1/extractor with the filing accession number when you need the entire classified filing.

A specific filing item

  1. 1Find the filing
  2. 2Retrieve the accession number
  3. 3Select the filing item
  4. 4Extract the item
  5. 5Receive text or HTML

Use GET /v1/extractor/item with the accession number and item number when you only need one classified section.

Supported Output Formats

Extracted filing content can be returned in two formats, depending on how the data will be used.

Choose the format that fits the pipeline

FormatTypical Use Cases
Plain textAI pipelines, NLP, search indexing, analytics
HTMLDocument rendering, web applications, preserving formatting

Applications can choose the format that best fits their processing pipeline without downloading and parsing the original filing document.

Example Extraction Request

To retrieve a specific filing item, specify the filing accession number, item number, and desired output format. The API returns the requested filing item as structured text.

GET /v1/extractor/item

http
GET /v1/extractor/item?accession_number=0000123456-24-000001&item_number=1A&type=text

For complete filing extraction, use the /v1/extractor endpoint without selecting an individual filing item.

Build SEC Content Processing Workflows

Extracted filing content can serve as the foundation for document analysis, search, and AI workflows. After identifying a supported filing, applications can retrieve its complete extracted content or select a specific filing item for downstream processing without parsing the original SEC document.

A typical item-level workflow

  1. 1Search filings
  2. 2Select the filing
  3. 3Choose the filing item
  4. 4Extract content
  5. 5Analyze, index, or store

Structured filing content can also be combined with other SEC Filings API capabilities, such as downloading original filing documents or converting XBRL filings into structured JSON, depending on the application requirements.

From discovery to extracted content

  1. Search filings
  2. Select filing
  3. Choose item
  4. Extract content
  5. Analyze or store

Why Developers Extract Filing Content

Structured filing content reduces the complexity of working with supported SEC forms by eliminating much of the document parsing typically required when processing EDGAR documents.

Common use cases

  • build AI and RAG applications using regulatory filings
  • index filing sections for search
  • analyze disclosures across companies and reporting periods
  • automate compliance and regulatory monitoring
  • process specific filing items without downloading complete documents
  • generate summaries and insights from filing content
  • support financial research and analytics workflows
  • integrate filing content into internal data pipelines
Extracted Filing Content

Start Extracting SEC Filing Content

Retrieve structured text or HTML content through the FinFeedAPI SEC Filings API.

Extract complete filing content or individual filing items without manually parsing EDGAR documents, and integrate the results into AI applications, search platforms, analytics systems, or regulatory workflows.