The SEC EDGAR API: Free Fundamental Data for Developers
Before you pay for a fundamentals API, know that the SEC gives away structured financial-statement data through EDGAR. Here's what the API offers, its quirks, and how to actually use it.
There’s a reflex among developers building finance tools to immediately shop for a fundamentals API and start paying a monthly fee. Sometimes that’s right. But for US-listed companies, the most authoritative source of fundamental data is free and comes straight from the regulator: the SEC’s EDGAR system, which exposes a public JSON API over the same data every filing is built from. This is a practical guide to what it offers and where it’ll trip you up. None of this is investment advice.
What EDGAR actually gives you
EDGAR is the SEC’s electronic filing system, and in recent years the SEC has put clean JSON endpoints in front of it. The two you’ll use most return a company’s submission history (every filing, with type and date) and its XBRL “company facts” — the structured financial data points pulled from filings, like revenue, net income, assets, and shares outstanding, with their reporting periods.
Because this data is sourced from the filings themselves, it’s authoritative in a way that aggregated third-party feeds aren’t. When a vendor’s number disagrees with EDGAR, EDGAR is the reference. For valuation models, screeners, and any tool where being wrong about reported financials is unacceptable, that matters.
The quirks you’ll hit
EDGAR is free and authoritative, but it was built for regulatory disclosure, not for quants, and it shows.
XBRL tags are inconsistent across companies. The same economic concept can be reported under different tags, and companies use custom extension tags. “Revenue” might appear as Revenues, RevenueFromContractWithCustomerExcludingAssessedTax, or a company-specific variant. You can’t assume one tag works everywhere — you’ll write fallback logic that checks several tags per concept.
It’s company-by-company. There’s no single endpoint that returns “every company’s revenue for Q3.” You query one CIK at a time and assemble universes yourself, which means caching and batch jobs if you want broad coverage.
You must send a User-Agent header. The SEC requires requests to identify you (typically a contact email) and enforces a fair-access rate limit. Hammer it without a proper header and you’ll get blocked. This catches everyone once.
A sane way to use it
The pattern that works: download and cache the ticker-to-CIK map once, then for each company you care about, pull its company-facts JSON and extract the concepts you need with a tag-fallback dictionary. Store the results in your own database keyed by CIK, concept, and period. Refresh on a schedule that matches filing cadence — quarterly and annual reports don’t change daily.
Treat EDGAR as your source of truth for reported fundamentals and layer faster, more convenient APIs on top only where you need coverage EDGAR doesn’t provide easily — like real-time prices, which EDGAR doesn’t do at all. EDGAR is for what companies reported, not for what they’re trading at right now.
For a developer building a stock screener, a valuation dashboard, or a research notebook on US issuers, starting with EDGAR means your foundational data is free, authoritative, and never gated behind a vendor’s pricing change. The cost is the engineering to tame XBRL. For a lot of projects, that’s a trade worth making.
FAQ
Is the EDGAR API really free?+
Does it cover non-US companies?+
Why not just use a paid fundamentals API?+
Before your next finance project signs up for a fundamentals subscription, spend an afternoon with EDGAR. For US companies, the regulator already gives away the most trustworthy version of the data — you just have to do a little work to read it.
Related reading
2026-06-08
Alpaca API Review: Commission-Free Automated Trading for Developers in 2026
Alpaca markets itself as an API-first brokerage. After building against it, here's where the developer experience shines, where paper trading hides real-world friction, and who it's actually for.
2026-06-08
IBKR vs Alpaca for Automated Retail Trading in 2026
Interactive Brokers and Alpaca sit at opposite ends of the brokerage-API spectrum: depth and complexity versus simplicity and speed. Here's how to choose based on what you're actually building.
2026-06-08
Position Sizing with the Kelly Criterion: A Developer's Guide
The Kelly criterion gives a mathematically optimal bet size, but applied naively to trading it will ruin you. Here's the intuition, the formula, and why almost everyone uses a fraction of it.
2026-06-08
Tiingo vs EODHD vs Databento: Market Data APIs Beyond the Usual Two
Polygon and Alpha Vantage get all the attention, but Tiingo, EODHD, and Databento each fill a different gap for retail quants. Here's how they compare on coverage, cost, and what you actually get.
2026-06-05
The Best Books on Behavioral Finance and Market History (2026)
Four research-backed books on why markets misbehave and why investors do — bubbles, manias, cognitive bias, and fractal risk — chosen for readers who want history and psychology, not stock tips.
Get the best tools, weekly
One email every Friday. No spam, unsubscribe anytime.