Data Feed
Fundamentals (Point in Time)
What the financial statements said, as known on each date.
01Overview
Every SEC filer's XBRL financial statements, mapped to standard line items and stamped at the moment EDGAR accepted the filing. A restated number becomes a new version; the earlier one stays queryable, so a backtest only ever sees what was public at the time.
Questions it answers
- What revenue, earnings and balance-sheet figures had a company reported as of a given date?
- Which numbers were later restated, and when?
Use cases
- Point-in-time backtests free of look-ahead bias
- Screens on standardized line items
- Tracing any figure to its filing, tag and JSON path
- Coverage
- 5,911,437 values; 3,095 companies
- History
- Periods back to 1980; filings published since 2009
- Also measured
- Median history per company 16.8 years; median capture 16.6 minutes after acceptance
- Update frequency
- Every 10 minutes
- Key fields
- Standardized line items, the as-reported XBRL tag, fiscal period, filing accession and acceptance time
- Point in time
- Bitemporal: publication time is the EDGAR acceptance timestamp; restatements are new versions
- Sources
- SEC EDGAR XBRL company facts API · OpenFIGI, GLEIF and SEC identifier files (for the security master)
- Licence
- Public domain (SEC)
- Delivery
- Data API · MCP · Python SDK · Excel · S3/Snowflake files · App
Data as of 2 November 2026
02How point in time works
Each value carries the time it became public and the time Factget first saw it. Corrections and restatements are new versions; earlier versions stay queryable, so a backtest only sees what was known on each date. The source file behind every value is stored unaltered.
Talk to us
Build a datasetfrom your sources.
Tell us the sources and the fields you need. We’ll show you what factget can build, and keep current.