Skip to main content
Use this page when you need a production SEC EDGAR API instead of a raw filing-download script. SEC API indexes EDGAR filings and exposes them through REST, SDKs, CLI, and hosted MCP with normalized schemas, cursor pagination, request IDs, source URLs, accession numbers, and freshness metadata.

Evaluate filing search

Test issuer resolution, filing lookup, source trails, and the first useful EDGAR workflow.

Open the API reference

Inspect exact endpoints, parameters, response fields, and examples.

Get an API key

Create an account and run a source-cited EDGAR request.

​
What SEC API adds on top of raw EDGAR

No SGML/HTML parsing

EDGAR is the official source. SEC API adds parsed filing manifests, normalized identifiers, section access, compact response shapes, and JSON contracts so your code does not start with SGML, HTML, and XBRL cleanup.

Source trail included

Filing-derived responses preserve the fields an audit trail needs: CIK, form, accession number, filing date, source URL, request ID, freshness, and materialization metadata where the endpoint returns it.

Agent-sized payloads

Use filing search, section retrieval, statements, facts, and semantic search to give an agent the narrow evidence it needs instead of dropping a full filing into context.

One contract across tools

Run the same workflow from REST, SDKs, CLI, or hosted MCP. That matters when a human prototype becomes an automated monitor or coding-agent task.

​
What you can build

  • Financial research platforms — Pull income statements, balance sheets, and cash flows for any public company
  • Compliance monitoring — Watch for new filings, enforcement actions, and insider transactions in real time
  • Investment analytics — Track institutional holdings, executive compensation, and ownership changes
  • AI agents — Feed structured SEC data to LLMs via REST or hosted MCP

​
What to verify in an EDGAR API evaluation

A serious evaluation should not stop at “can I get a filing?” Pick one real issuer and one investor workflow, then verify:
  • the issuer was resolved by ticker, CIK, or company name
  • the filing response preserved form type, accession number, filing date, and source URL
  • the payload was narrow enough for an agent to use without ingesting the full raw filing
  • the response included request metadata your logs can preserve
  • the same workflow can be repeated through REST, SDKs, CLI, or MCP
  • pricing and limits are acceptable for your expected fanout

​
Quick start

Get Apple’s latest 10-K filing in one request: 
curl -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/filings/latest?ticker=AAPL&form=10-K"

{
  "accession_number": "0000320193-24-000081",
  "form": "10-K",
  "filed_at": "2024-11-01",
  "company_name": "Apple Inc",
  "cik": "0000320193"
}
Pull structured financial statements: 
curl -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/statements/all?ticker=AAPL&period=annual&limit=1"

​
Common endpoint families

Data typeEndpointCoverage
Filings/v1/filingsAll SEC form types since 1993
Financial statements/v1/statementsIncome, balance sheet, cash flow
XBRL facts/v1/factsAll XBRL-tagged concepts
Ownership (13F)/v1/owners/13fInstitutional holdings quarterly
Insider transactions/v1/insidersForm 3, 4, 5 transactions
Enforcement actions/v1/events/enforcementSEC administrative proceedings
Executive compensation/v1/compensationProxy statement (DEF 14A) data
Full-text search/v1/searchKeyword and semantic search
Subsidiaries/v1/companies/subsidiariesExhibit 21 data
Entity resolution/v1/entities/resolveTicker, CIK, CUSIP, FIGI, ISIN

​
Choosing between raw EDGAR and an API layer

Raw EDGAR is the right source of record when you want the official filing and you are prepared to own parsing, caching, identifier mapping, retries, and source normalization. SEC API is the right layer when you want those concerns handled behind a production contract and you need an agent or application to consume compact, source-cited JSON. Use the buyer-facing comparison pages when you are comparing commercial vendors:

Best SEC API for AI agents

Compare API, MCP, docs, and workflow-readiness criteria for agentic SEC data products.

sec-api.io alternative

Plan a fair migration proof from sec-api.io-style workflows to SEC API.

Raw EDGAR vs SEC API

Decide when raw SEC.gov/data.sec.gov is enough and when a production API layer is justified.

​
Agent prompt

​
SDKs and integrations

  • Python: pip install secapi-client
  • JavaScript/TypeScript: npm install @secapi/sdk-js
  • Rust: cargo add sec-api-sdk-rust
  • Go: go get github.com/secapi-ai/secapi-go
  • MCP: Hosted MCP server for Claude, ChatGPT, and other AI agents

​
Pricing

Start with 150 free API calls. Pay-as-you-go pricing scales by metered API family, and committed plans are available when your filing, statements, search, or agent workload is steady.

Get your API key

Create an account and start making source-cited EDGAR requests.

​
Resources