Data Quality

Coverage, refresh timing, and reliability notes for TickerDB

TickerDB is most useful when the state labels are dependable. This page explains what is covered, when data updates, and what integrity safeguards sit behind the API.

Coverage

TickerDB covers US stocks, ETFs, and supported crypto pairs. Public responses expose asset_class so clients can distinguish stocks from ETFs and crypto, and stock-only fundamental sections are omitted for non-equities.

Freshness

TickerDB is end-of-day only. Responses expose data_status for the freshness mode and as_of_date for the specific session date represented by the snapshot.

TickerDB is end-of-day only. Stocks and ETFs refresh by ~00:30 America/New_York (Eastern time, EST/EDT). Crypto refreshes by ~00:10 UTC, including weekends.

Corporate Actions

Historical classifications are computed on adjusted market data so stock splits and similar corporate actions do not create false technical regime shifts. If a response is available for a given historical date, it is meant to reflect the post-adjustment view of that session.

Universe Quality

Only active tradable assets are published into the current API surface. Unsupported or inactive symbols are excluded from watchlist additions and summary lookups.

Classification Integrity

TickerDB stages publish candidates before promoting them into the serving tables. Snapshot rows, support and resistance rows, sector aggregates, and band transitions are validated during that publish flow so incomplete runs do not silently replace the active dataset.

How To Use This Safely

Use as_of_date and the band stability metadata together. The date tells you which session is being described, and the stability metadata helps you judge whether a label is brand new or well established.