Industrial REITs Data: Filing Facts, Sector Benchmarks and Demand Indicators · Head-to-head
SEC EDGAR XBRL companyfacts API vs SEC EDGAR Full Filing Index by CIK
Which industrial reits data: filing facts, sector benchmarks and demand indicators data fits your job: SEC EDGAR XBRL companyfacts API, or SEC EDGAR full filing index by CIK. API, files, or your warehouse. Daily, weekly, or hourly.
SEC EDGAR XBRL companyfacts API
SEC EDGAR full filing index by CIK
Coverage, side by side
| SEC EDGAR XBRL companyfacts API | SEC EDGAR full filing index by CIK | |
|---|---|---|
| Geographic | United States - all EDGAR filers, including every US-listed industrial REIT | United States - all EDGAR filers, including every US-listed industrial REIT |
| Temporal | Full filing history per registrant; Prologis revenue facts verified from CY2016 through CY2026Q1 | Verified Prologis history back to 1997-09-18 across archived and recent records |
| Granularity | One fact per reported concept per period per filing | One record per filing, with document-level links beneath each accession |
What each contains
Pick by fit, not by loyalty.
| SEC EDGAR XBRL companyfacts API | SEC EDGAR full filing index by CIK | |
|---|---|---|
| Geography | United States - all EDGAR filers, including every US-listed industrial REIT | United States - all EDGAR filers, including every US-listed industrial REIT |
| Temporal reach | Full filing history per registrant; Prologis revenue facts verified from CY2016 through CY2026Q1 | Verified Prologis history back to 1997-09-18 across archived and recent records |
| Granularity | One fact per reported concept per period per filing | One record per filing, with document-level links beneath each accession |
| Unit of analysis | Registrant x XBRL concept x reporting period | Registrant x filing x primary document |
| Scale | ~3.5 MB of facts per large filer; 586 us-gaap concepts for Prologis with hundreds of dated facts per concept | ~1,002 recent filings per registrant with ~1,951 more in the deeper archive |
| Field dictionary | 14 fact-level fields - identifier, taxonomy, label, definition, units, period, value, accession, form, dates, frame | 11 index-level fields - identifiers, ticker, SIC, accession, form, filing date, report date, primary document |
Or take both in one feed
They are less rivals than two halves of one workflow, joined on the accession number both sides carry. A typical industrial REITs build runs the index first - enumerate the registrant's filings, filter to 10-K and 10-Q, note report dates and acceptance timestamps - then opens the fact layer for the periods those filings cover, pulling Revenues, NetIncomeLoss and Assets as tagged values instead of parsed tables. Run it in reverse just as easily: take a suspicious fact from companyfacts, read its accn, and the index supplies the filing date, form and primary document behind it.
Two practical notes from the records. Mind the calendar asymmetry: the index stamps filings by submission date and report date separately, while facts key to fiscal year and period - a December fiscal year keeps these aligned, anything else needs a small mapping. And respect the coverage boundary: FFO is non-GAAP and not an XBRL concept anywhere, so the derived measure comes from fact-layer net income plus adjustments, while the portfolio metrics stay document-bound. Or take both in one feed.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Is SEC EDGAR XBRL companyfacts better than the SEC EDGAR full filing index?
For numbers, yes; for events, no. Companyfacts turns every registrant's filings into modeled-ready data - 586 us-gaap concepts for Prologis with per-fact filing references - while the full filing index tracks the filings themselves, including Form 4s and 8-Ks that produce no tagged facts. They answer different questions about the same registrants.
What do the two datasets have in common?
The regulator, the registrant universe and the join key. Both cover all EDGAR filers including every US-listed industrial REIT, both identify companies by Central Index Key, and both stamp records with the accession number of the underlying filing - so a fact on one side resolves to its document on the other.
Which dataset goes further back in time?
It depends on the axis. The filing index reaches furthest in raw terms: Prologis records verify back to September 1997, predating widespread XBRL adoption. Companyfacts hold full reporting history per company too, but verified Prologis revenue facts begin at CY2016, so deep historical work leans on the index side.
Can the filing index give me Prologis occupancy and same-store NOI?
Not directly, and neither can anything else in these two records. Those operating metrics sit in MD&A narrative and exhibit tables inside the primary documents the index links to - pld-20251231.htm under a specific accession. The index gets you to the document; extraction from there is a parsing job, not a lookup.
Do I need both datasets for industrial REITs work?
Most serious workflows end up using both. Structured screens, factor construction and statement modeling run entirely on companyfacts; event surveillance, pre-XBRL history and document retrieval need the index.
Which should a quant covering industrial REITs sample first?
Companyfacts first if the output is a model, the index first if the output is a watchlist. Quant teams building cross-sectional fundamentals across Prologis, EastGroup, STAG and peers start with the fact layer; teams tracking filing flow and disclosure changes start with the index. Sample both and match each to the question.