What Is the Difference Between SEC Filing Metadata, Full-Text Search, Extractor, and XBRL Converter?

SEC filings contain far more than annual reports and quarterly statements.

Every filing consists of multiple layers of information.

Some describe the filing itself.

Others contain the complete filing text.

Some organize disclosures into structured sections… while others expose machine-readable financial statements through XBRL.

Treating all of these as the same type of data often leads developers down the wrong path.

They download large EDGAR documents when all they needed was metadata. They search filing text when they actually needed structured financial statements. Or they parse HTML manually instead of using an extraction endpoint built for the job.

The FinFeedAPI SEC API separates these different layers into purpose-built tools, allowing you to retrieve exactly the information you need without unnecessary processing. Depending on your workflow, you can search filing metadata, search document contents, extract classified disclosure sections, download original filing files, or convert XBRL financial data into structured JSON.

Let’s explain what each capability does, when to use it, and how they work together in real-world SEC data pipelines.

One Filing. Four Different Layers of Information.

A common misconception is that an SEC filing is just one document.

In reality, every filing contains several distinct layers, each serving a different purpose.

The first layer is metadata: information describing the filing itself, such as the company, filing date, accession number, form type, report date, and whether XBRL data is available.

The second layer is the document text: where disclosures, legal language, management commentary, and business descriptions live.

The third layer organizes that text into meaningful sections such as Risk Factors, Business Overview, or individual 8-K event items.

Finally, many filings also include XBRL, a structured representation of financial statements designed for machines rather than humans.

Each layer answers a different question:

Understanding this distinction makes building SEC-powered applications much simpler.

SEC Filing Metadata: Finding the Right Filing

Every workflow starts with one simple question:

Which filing should I analyze?

That's exactly what filing metadata is designed to answer.

Instead of downloading thousands of SEC documents and filtering them yourself, the Filings endpoint returns structured information describing every filing available in the database.

Think of metadata as the catalog for the SEC archive.

It doesn't contain the filing text itself. Instead, it tells you everything you need to identify the correct filing before performing more advanced operations.

Typical metadata includes:

• accession number
• CIK
• ticker
• form type
• filing date
• report date
• SEC acceptance timestamp
• filing size
• primary document
• source file
• XBRL availability
• Inline XBRL availability

Because every filing receives a unique accession number, metadata becomes the bridge to every other API capability.

Once you have the accession number, you can retrieve classified filing sections, download original filing files, or convert XBRL into JSON.

Powerful filtering without downloading documents

Metadata queries support filters including:

• ticker
• CIK
• form type
• filing date ranges
• report date ranges
• filing items
• sorting
• pagination

This allows you to answer questions like:

• Show every Apple 10-K since 2020.
• Find all 8-K filings submitted this week.
• Retrieve filings for companies with a specific CIK.
• Build a filing timeline for one issuer.
• Find filings containing Item 1.01.

Rather than processing millions of SEC documents, you receive only the filing records matching your criteria.

Metadata is discovery, not content

One of the biggest misunderstandings is expecting metadata to contain disclosure text.

It doesn't.

Metadata tells you that a filing exists and provides the identifiers needed to retrieve additional information later.

If you need to read the filing itself, you'll use the Extractor.

If you're looking for financial statement values, you'll use the XBRL Converter.

Metadata simply helps you find the correct filing first.

Full-Text Search: Finding Words Inside SEC Filings

Sometimes you don't know which company filed the document.

You only know the topic you're interested in.

Maybe you're researching cybersecurity incidents.

Maybe you're tracking discussions about artificial intelligence.

Maybe you're looking for companies mentioning supply chain disruptions.

Searching filing metadata won't help because those phrases aren't metadata—they appear inside the filing itself.

That's where Full-Text Search comes in.

Instead of filtering filing attributes, Full-Text Search scans the contents of SEC filing documents and returns filings containing the keywords you're looking for.

Search by meaning, not by company

The Full-Text endpoint supports keyword-based discovery across filing documents.

You can search for terms that must appear in the filing, exclude unwanted phrases, and combine those searches with form types and filing date ranges.

For example:

• Find every 8-K mentioning "material agreement."
• Search 10-K filings discussing cybersecurity.
• Locate filings referencing a specific product.
• Find disclosures mentioning tariff exposure.
• Search historical filings for "AI infrastructure."

The search is case-insensitive and supports partial word matching, making it practical for large-scale document discovery.

Full-Text Search is not an extractor

A common mistake is assuming Full-Text Search returns the relevant paragraph.

It doesn't.

Instead, it answers a simpler question:

Which filings mention these words?

The response contains filing information such as:

• accession number
• company name
• form type
• filing date
• document filename
• document description

Once you've identified the filing you're interested in, you can use its accession number with the Extractor to retrieve the actual disclosure text.

This two-step workflow is significantly faster than downloading and parsing every filing yourself.

Typical use cases

Full-Text Search is particularly useful for:

• compliance monitoring
• news and event detection
• research pipelines
• AI-powered document retrieval
• legal analysis
• thematic investing
• disclosure monitoring
• alert systems

Instead of searching by company, you're searching by information.

That's an important distinction—and one that makes Full-Text Search one of the most powerful discovery tools in the FinFeedAPI SEC API.

Extractor: Reading SEC Filings Without Parsing HTML

Once you've identified the filing you need, the next challenge is reading it.

While every filing is available through EDGAR, the raw documents are designed primarily for human readers. They often contain complex HTML, inconsistent formatting, exhibits, tables, and section layouts that vary between forms and companies.

Parsing those documents manually quickly becomes a maintenance problem.

The Extractor endpoint solves this by retrieving filing content directly from EDGAR and organizing it into structured disclosure sections. Instead of working with raw HTML, you receive content already classified according to the filing type.

For supported forms… including 8-K, 10-K, and 10-Q, the API understands the filing structure and separates the document into logical items.

For example:

• 8-K filings are classified by event items such as 1.01, 2.01, or 7.01.
• 10-K and 10-Q filings are organized according to their Part and Item structure, including sections such as Business, Risk Factors, and Properties.

The Extractor supports two different workflows.

The first returns the entire classified filing, making it useful when you want to analyze every disclosure section.

The second retrieves only a single filing item, allowing you to request just the section you care about.

For example, instead of processing an entire 10-K, you can retrieve only:

• Item 1A: Risk Factors
• Item 7: Management's Discussion and Analysis (MD&A)
• Item 1.01 from an 8-K: Entry into a Material Definitive Agreement
• Item 5.02 from an 8-K: Director or Executive Officer Changes

Because the API returns either plain text or HTML, downstream applications don't need to spend time locating section boundaries or cleaning SEC document markup.

For AI agents, search systems, and event-monitoring pipelines, this significantly reduces preprocessing while improving consistency.

XBRL Converter: Turning Financial Statements into JSON

Narrative disclosures are only one part of an SEC filing.

Many filings also include XBRL (eXtensible Business Reporting Language) a machine-readable representation of financial statements and accounting disclosures.

This is where another common misunderstanding appears.

Many developers assume XBRL is simply another version of the filing text.

It isn't.

XBRL contains structured financial facts, not narrative language.

Instead of paragraphs, it stores tagged accounting values such as:

• revenue
• operating income
• assets
• liabilities
• cash flow
• earnings per share
• accounting policies
• reporting periods
• units of measure
• dimensional data

The XBRL Converter transforms these XBRL documents into structured JSON that applications can consume immediately.

Rather than parsing XML schemas, taxonomies, namespaces, and relationships yourself, you receive organized JSON containing financial statements, company information, filing metadata, and accounting disclosures.

The converter supports three input methods:

• accession number
• SEC filing HTML URL
• XBRL XML URL

Only one input is required, making it easy to integrate into existing workflows.

Typical applications include:

• financial modeling
• earnings analysis
• quantitative research
• machine learning pipelines
• accounting systems
• structured financial databases

If your goal is to read Risk Factors or Management Discussion, use the Extractor.

If your goal is to analyze revenue growth, cash flow, or balance sheet values, use the XBRL Converter.

How These Tools Work Together

Although each capability solves a different problem, they're designed to work together.

A typical workflow begins with Metadata, where you identify the filings matching your company, form type, or reporting period.

If you're researching a topic instead of a company, you can start with Full-Text Search to discover filings mentioning specific words or phrases.

Once you've identified the filing, the returned accession number becomes the bridge to every other operation.

You can:

• extract the complete filing,
• retrieve only a specific disclosure item,
• download the original EDGAR source files,
• or convert XBRL financial statements into JSON.

Instead of downloading every filing and building your own parsing pipeline, each endpoint performs one specific task exceptionally well.

Which Tool Should You Use?

Common Misconceptions

1. Metadata contains the filing

It doesn't.

Metadata describes the filing and helps you find it. The filing text lives elsewhere.

2. Full-Text Search returns the relevant paragraphs

It doesn't.

It finds filings containing your keywords. Use the Extractor to retrieve the actual disclosure text.

3. Extractor and XBRL Converter do the same thing

Not at all.

The Extractor returns narrative disclosure content.

The XBRL Converter returns structured financial facts.

4. XBRL is only available for annual reports

Not necessarily.

The XBRL Converter supports multiple filing types, including 10-K, 10-Q, 8-K, S-1, S-3, 20-F, and 40-F.

Choosing the Right Tool Makes SEC Data Much Easier

SEC filings aren't just documents.

They're a collection of structured metadata, searchable disclosure text, classified filing sections, financial statement data, and original source files.

FinFeedAPI separates each of these layers into dedicated API endpoints, allowing developers to retrieve only the information they actually need instead of downloading and processing entire EDGAR filings.

Whether you're building an earnings monitor, an AI research assistant, a compliance platform, or a financial modeling pipeline, choosing the right endpoint makes your application faster, simpler, and easier to maintain.

Build Smarter Applications on Top of SEC Data

Instead of maintaining your own EDGAR parsing infrastructure, build on top of structured SEC data.

With FinFeedAPI, you can:

• discover filings through structured metadata,
• search millions of filing documents by keyword,
• extract complete filings or individual disclosure sections,
• convert XBRL financial statements into structured JSON,
• access the same capabilities through REST, WebSocket, JSON-RPC, and MCP interfaces.

Start with the endpoint that matches your workflow and let the API handle the complexity behind the filing.

Explore the SEC API, experiment with different endpoints, start building your workflows and let the API handle the complexity behind the filing.

Related Topics

• How Can You Search Inside SEC Filing Documents?
• Why Use an API Instead of Downloading SEC Filings Manually?
• Prediction Markets: Complete Guide to Betting on Future Events
• Markets in Prediction Markets
• What Is the Best Way to Build Real-Time SEC Filing Alerts?
• How Can AI Agents Access and Process SEC Filings?