Feature panel

READ ONE DERIVED FEATURE PANEL — the model-ready research features this platform computes for itself: price/return and liquidity features, monthly fundamentals, analyst-estimate dynamics, options and volatility-surface features, insider and institutional-ownership features, news-sentiment features, betas, regime and macro features. Discover the slugs via /api/v3/features/datasets — they are product names, not table names. With ?ticker= you get that symbol's observations newest first; without it you get the LATEST cross-section (every symbol on the most recent observation date), which is bounded by construction rather than by sorting the whole panel. observation_date is the date the row describes; a panel that carries a vintage serves it beside it (ratio_vintage on the monthly fundamentals: when the valuation ratios were published; returns_data_through on the betas: where the return history behind the estimate ends), and rows dated after today, or monthly rows written before their month ended, are not served. Symbols resolve through the shared security resolver first and identity.identity_verified states whether the read was keyed on an authoritative identifier or on the resolved security's symbol; an ambiguous symbol is refused, never guessed. Every response carries the dataset's measured coverage (rows_total, symbols_total, observation_dates, history window) and its freshness, so an empty rows array arrives beside the count of symbols that DO have rows and can never be read as a dead upstream — result is the machine-readable outcome (rows, no_rows_for_symbol, no_rows_in_window). An archival dataset (producer stopped, or data behind its own rhythm) is served for its history, and every response says so rather than implying currency. An unknown or withheld slug — including one whose measured freshness is withheld (404 dataset_withheld, with reason and freshness) — is a 404 and an unreadable store is a 503 — both refunded, because a billed 200 over an empty array is the defect this endpoint exists to remove.

A 200 is a JSON envelope: ok: true and this endpoint's own fields (see Research Datasets). It carries X-Request-ID, the credit headers (X-Credits-Cost, X-Credits-Remaining, X-Credits-Receipt, X-Credits-Settlement) and the rate-limit headers.

A 200 is billed even when it holds no data (an empty list, null, found: false), so check those fields. Pricing & credits explains the credit headers.

No error is billed. The body is { "ok": false, "error", "detail", "request_id" }; read the code from error.

This table lists what the spec declares for this route. Error responses lists every code FIRM sends, with when to retry.

Read the Research Datasets guide for this endpoint's fields and examples.