Gotchas
Things that have caught real users.
BTC is not bitcoin
Symbols are namespaced by asset class.
Passing BTC to a stock endpoint returns the Grayscale Bitcoin Mini Trust ETF (a real US-listed equity with that ticker), not bitcoin spot. If you want the crypto, use X:BTCUSD. Same rule for GOLD (Gold.com, an equity) vs X:XAUUSD (gold spot). See Tickers for the full prefix table.
Rates have no session_open / session_high / session_low
A rate is one value per business day.
On rates the session signals are null, not 0, so a filter like session_high > 0 drops them. Reach for price and the daily signals instead.
Numeric literals are fully specified
Numbers are plain numerals.
Write 1500000000 or 1.5e9, not 1.5B. Write 5 for 5% on percent signals like change_1d_pct, not 0.05: percent signals are whole percent, not fractions. Scales vary by signal, so check its description in the signal catalog.
Edge-triggered booleans stay true all session
One firing, sticky until the next reset.
Booleans like sticky_breakout, gap_up and golden_cross are edge-triggered: they flip true the moment the condition is met and stay true for the rest of the trading session even if the underlying condition reverses. They reset at the start of the next session. If you're asking “is this happening right now,” use the continuous flavor of the boolean (e.g. above_yesterday_high); if you're asking “did this happen today,” the edge-triggered one is what you want.
Daily-only signals can’t be pulled at 1m or 1h
SMAs, RSI, MACD, fundamentals: daily snapshots only.
Asking /v2/tickers/NVDA/history?select=rsi_14&grain=1m returns 400: Signal “rsi_14” is daily-only — request it at grain=1d. Request 1d for any slow-moving signal. The signal catalog labels each signal with the grains it's stored at (grains on List signals); filter with grain=1m for the signals stored every minute.
1q results are keyed by calendar quarter
52/53-week fiscal filers don't end quarters on calendar boundaries.
On /v2/tickers/{ticker}/history?grain=1q, t is the calendar quarter of the fiscal period end (2026-Q2) so off-calendar fiscal years still align cross-ticker. A period that ends in the first seven days of a calendar quarter counts toward the quarter before it, so a 53-week quarter ending 2023-07-01 is 2023-Q2. Read each result's fiscal_period for the exact period-end date; don't assume it's the calendar quarter's last day. Quarterly signals also can't mix with daily ones in a single request (the grids aren't joinable: 400 by design).
On a report day, live and history disagree
Both are right: the live value is now, the historical value is the state at that day's close.
On a post-market report day, the live ticker shows the new report that evening, while that day’s history keeps the prior one. On July 30, 2026, AAPL’s live last_reported_eps read 2.02 after the release; the history for July 30 reads 2.01. See As-of › When a report counts as public.
as_of means different things on different endpoints
Live time vs requested date.
On live endpoints as_of is the server time at which the response was assembled. On as-of reads (/v2/tickers/{ticker}?asof=, scan with asof) it is the date or timestamp you passed (a bare date means that day’s close). An old as_of on those calls is the answer, not stale data. Neither is the market-data time: that is price_asof, and it dates the live signals only (price, volume, session, intraday indicators). Every other signal is as of the last run of its catalog refresh. More in Signals › The as_of timestamp.
kind=signal needs the signal named to use the grammar
A q that works on kind=analyst needs one more param on kind=signal.
A filter on payload can’t use an index, so q and join=state require signal=<name>, which binds the query to one. Named that way, a week of golden_cross entries across the whole market comes back in milliseconds; unnamed, the request is refused with a 400 naming the param to add. transition=enter|exit is an ordinary filter here, not a second requirement.
group_by is not available on this kind: an aggregate has no limit to stop at, so it reads every firing in the window. Filter mode needs none of this.
Built-in universe ids are reserved
top_10 and top_100 are shared, read-only universes.
When you fetch /v2/universes/top_10 you get a built-in universe, even though you didn't create one. You can't create a universe with a built-in id (a 400 on POST). You can't delete or edit a built-in universe either; both come back 403.
Deleting a webhook deletes its deliveries
To pause one instead, disable it.
DELETE /v2/webhooks/{webhook} removes the webhook and every delivery with it, queued retries included, so nothing queued fires afterward and its delivery log is gone. A POST already in flight at that moment can still arrive once. To stop deliveries and keep the log, PATCH it with enabled: false.