May 09, 2026

How Can You Search Inside SEC Filing Documents?

featured image

SEC filings contain some of the most valuable company information available publicly. Earnings risks. New agreements. Executive changes. Legal disputes. Acquisition plans. Debt updates.

But finding that information is harder than it sounds.

Most SEC filing tools only let users search metadata like ticker symbols, company names, form types, or filing dates. That works when you already know exactly what you are looking for.

The problem starts when you need to search inside the actual filing documents.

For example:

  • Find every 8-K mentioning “material agreement”
  • Search 10-K filings for “cybersecurity”
  • Discover filings that mention “AI infrastructure”
  • Exclude filings containing certain keywords
  • Track new filings discussing “bankruptcy” or “restructuring”

This is where full-text SEC filing search becomes important.

Metadata helps identify filings at a high level. You can filter by:

  • company
  • ticker
  • form type
  • filing date
  • report date

But metadata does not tell you what is written inside the filing itself.

Imagine searching for all 8-K filings related to supply chain disruptions. There is no dedicated SEC field for that topic. The only way to find it is by searching the actual document text.

The same applies to:

  • risk disclosures
  • partnership announcements
  • financing agreements
  • litigation mentions
  • executive compensation discussions
  • AI and crypto references
  • regulatory concerns

Without full-text search, teams often end up downloading and parsing thousands of filings manually.

That process is slow, expensive, and difficult to scale.

The FinFeedAPI SEC API includes a dedicated endpoint for searching inside SEC filing documents:

1GET /v1/full-text

nstead of searching only filing metadata, this endpoint searches the actual filing content.

That means developers can build tools that discover filings based on words, phrases, or topics mentioned in the document.

The /v1/full-text endpoint supports several useful filters.

Search for keywords that must appear in the filing document.

Example:

1text_contains=material agreement

You can also provide multiple keywords separated by commas.

Example:

1text_contains=cybersecurity,artificial intelligence

This is useful for:

  • news monitoring
  • compliance workflows
  • AI research pipelines
  • market intelligence tools
  • alert systems

Exclude filings containing specific keywords.

Example:

1text_not_contain=bankruptcy

This helps reduce noisy search results.

For example, you might want filings discussing acquisitions but not restructuring events.

You can narrow searches to specific SEC forms.

Examples:

  • 8-K
  • 10-K
  • 10-Q
  • S-1
  • 20-F

Example:

1form_type=8-K

Or multiple forms:

1form_type=10-K,10-Q

This matters because different forms serve different purposes.

  • 8-K filings focus on material events
  • 10-K filings contain annual business and risk information
  • 10-Q filings provide quarterly updates

Filtering by form type keeps searches more relevant.

The API also supports date-based filtering:

1filling_date_start=2025-01-01
2filling_date_end=2025-12-31

This is especially important for:

  • recent event monitoring
  • historical research
  • backtesting workflows
  • AI data pipelines
  • market event analysis

The API uses the exact schema names:

  • filling_date_start
  • filling_date_end

Here is an example request searching for recent 8-K filings mentioning “material agreement”.

1curl -X GET "https://api.sec.finfeedapi.com/v1/full-text?form_type=8-K&text_contains=material agreement&filling_date_start=2025-01-01&filling_date_end=2025-12-31&page_size=25&page_number=1" \
2-H "Authorization: YOUR_API_KEY"

The API returns filing metadata for matching documents.

Example:

1{
2  "accession_number": "0001140361-21-012345",
3  "form_type": "10-K",
4  "filing_date": "2021-03-15",
5  "company_name": "Example Corporation",
6  "cik": 1234567890,
7  "document_filename": "form10k.htm",
8  "document_description": "Form 10-K Annual Report",
9  "source_file": "edgar/data/1234567890/0001140361-21-012345.txt"
10}

Once you have the accession number, you can continue the workflow with other SEC API endpoints.

For example:

  • extract a specific filing section with /v1/extractor/item
  • extract the full filing with /v1/extractor
  • download raw files with /v1/download
  • convert XBRL data into JSON with /v1/xbrl-converter

Track filings mentioning topics like:

  • AI
  • cybersecurity
  • tariffs
  • lawsuits
  • debt refinancing
  • mergers

Monitor new filings for material business updates before they appear in news summaries.

Feed highly targeted SEC filing content into AI systems instead of entire filing archives.

Search for regulatory language or disclosure trends across industries and time periods.

The same full-text search capability is also available through the FinFeedAPI MCP server.

This allows AI agents and MCP-compatible tools to search SEC filing documents directly using structured tool calls.

Typical workflow:

  1. Search filings using fulltext_search
  2. Retrieve accession numbers
  3. Extract filing sections with extractor_extract_item
  4. Process the results downstream with AI or analytics systems

If you’re building:

  • SEC monitoring tools
  • AI research workflows
  • Filing alert systems
  • Trading platforms
  • Financial dashboards
  • Market intelligence products

…access to structured SEC filing data matters.

FinFeedAPI SEC API helps developers:

  • search filing documents
  • stream new filings in real time
  • extract filing sections
  • download EDGAR files
  • convert XBRL into JSON

all through developer-ready APIs and MCP tools.

👉 Explore FinFeedAPI SEC API and build on top of real-time SEC filing data.

Stay up to date with the latest FinFeedAPI news

By subscribing to our newsletter, you accept our website terms and privacy policy.

Recent Articles