Hotel & Resort REITs Data: Filings Facts, Price History and Travel Demand · Head-to-head
SEC XBRL Company Facts API vs Yahoo Finance Chart API
Which hotel & resort reits data: filings facts, price history and travel demand data fits your job: SEC XBRL Company Facts API, or Yahoo Finance Chart API. API, files, or your warehouse. Daily, weekly, or hourly.
SEC XBRL Company Facts API
Yahoo Finance Chart API
Where the fields line up
No shared field names. These two answer different questions.
| Field | SEC XBRL Company Facts API | Yahoo Finance Chart API |
|---|---|---|
cik | Central Index Key of the filer; the number that keys every join. | not in this set |
entityName | Registered registrant name exactly as it appears on filings. | not in this set |
label | Human-readable label attached to each XBRL concept, kept alongside its machine name so reports read naturally while joins still resolve. | not in this set |
val | Reported value in US dollars for the concept-period combination. | not in this set |
start / end | Beginning and end of the reporting period the fact covers; end-only for instant (balance sheet) items. | not in this set |
accn | Accession number of the filing that sourced the fact - the key back to EDGAR documents. | not in this set |
fy / fp | Fiscal year and fiscal period (FY, Q1-Q4) of the filing that reported the fact. | not in this set |
form | Form type that carried the fact. | not in this set |
filed | Date the source filing was accepted by EDGAR; lets you reconstruct restatement history. | not in this set |
frame | Calendar-aligned frame identifier assigned when the fact fits the SEC's canonical period grid. | not in this set |
timestamp | not in this set | documented |
open | not in this set | documented |
Coverage, side by side
| SEC XBRL Company Facts API | Yahoo Finance Chart API | |
|---|---|---|
| Temporal | Generally 2009-present, Host Revenues into 2008-era data, multiple vintages per period | Full life of the listing via range=max; intraday limited to recent windows |
| Granularity | Quarterly or annual periods per concept per filer | 1-minute bars (roughly 7-day lookback) up to monthly |
What each contains
They tie on 2 attributes. Pick by fit, not by loyalty.
| SEC XBRL Company Facts API | Yahoo Finance Chart API | |
|---|---|---|
| Datadory rubric | 10 out of 10 | 8 out of 10 |
| Publisher | U.S. Securities and Exchange Commission | Yahoo Finance |
| What a row is | One XBRL-tagged fact: concept, period, value, originating filing | One OHLCV bar: timestamp, open, high, low, close, volume, adjusted close |
| Identifier system | Central Index Key (Host Hotels CIK 1070750); tickers resolved separately | Ticker symbol (HST) echoed in the meta block |
| Documented fields | 10 documented structures including label, units, accn, fy/fp, form, filed, frame | 10 documented fields across quote arrays, adjclose, meta and events |
| Field definitions | Verified during research | Verified during research |
| Format delivered | JSON | JSON |
| Temporal reach | Generally 2009-present, Host Revenues into 2008-era data, multiple vintages per period | Full life of the listing via range=max; intraday limited to recent windows |
| Finest granularity | Quarterly or annual periods per concept per filer | 1-minute bars (roughly 7-day lookback) up to monthly |
| Sample scale | About 3 MB per issuer; 459 us-gaap concepts for Host Hotels; ~90 MB for a 30-name cohort | About 20-40 KB per ticker-year; 251 daily bars returned for a 1-year HST pull; 1-2 MB for 14 tickers over 5 years |
| Update cadence at source | Filing-driven | Realtime |
Where they're equivalent
More than the audited-versus-traded split implies.
- Both were field-verified during research, definitions checked against live responses - the standard met by 85.7 percent of cataloged datasets.
- Both cover the same issuers from opposite ends: every US-listed lodging REIT appears once as a registrant with tagged facts and once as a traded ticker with bars.
- Both denominate in US dollars and timestamp every observation, so a join key of identifier-plus-date exists even if nothing else does.
Or take both in one feed
Yes - as a fundamentals-plus-market overlay rather than a merge. The filings layer sets the denominator: tagged revenues, debt and lease income per period per filer.
Join discipline decides whether the overlay holds. Resolve identity once - CIK 1070750 and ticker HST are the same Host Hotels, but nothing in either payload says so. Align clocks deliberately: fiscal periods ending December 31 against trading days that end three weeks after the filing date, never the same instant. Expect no shared primary key beyond identifier-plus-date, and expect the fundamentals side to be sparse - a few hundred observations per concept - where the market side is dense. Datadory normalizes each record to its documented dictionary before anything ships, on one cadence - daily, weekly, or hourly - your call. Request a sample of either dataset to watch the rows validate before anyone commits. Or take both in one feed.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Do the two field dictionaries overlap?
On three concepts only: an identifier (CIK versus ticker), a timestamp, and dollar-denominated values. Beyond that they diverge by design. The filings dictionary spends its fields on provenance - accn, fy, fp, form, filed, frame - and the chart dictionary spends its fields on market structure - open, high, low, close, volume, adjclose and dividend event amounts.
Which record reaches further back for hotel & resort REITs?
Depends on the axis. Tagged fundamentals generally start around 2009 with the XBRL mandate era, though Host Hotels' Revenues concept reaches into 2008-era data.
Can I model REIT FFO from either record?
Not directly from either. Funds From Operations is management-defined and not an XBRL-tagged us-gaap concept - confirmed absent from Host Hotels' concept set - so FFO must be derived from GAAP components the Company Facts record does carry, or taken from earnings-release exhibits. The chart record expresses the same payout economics indirectly through dividend events alongside adjusted closes.
Can I get both records from Datadory?
Yes - sample both, pick by fit, or take both in one feed. Each arrives normalized to its documented field dictionary with sample rows attached for validation, delivered on one schedule - daily, weekly, or hourly - your call - next to the rest of the hotel & resort REITs catalog.