--- title: "Latest or dated ETF snapshot" method: GET path: "/api/v1/etf/{symbol}/snapshot" tags: ["Funds & ETFs"] --- # Latest or dated ETF snapshot `GET /api/v1/etf/{symbol}/snapshot` Single ETF snapshot at the latest cycle (default) or at a specific calendar date via ``?date=YYYY-MM-DD``. Returns the full payload: pricing (nav, price, premium/discount), fund characteristics (AUM, expense ratio, yields), top-10 holdings sample, sector weightings (both raw + canonical), asset-class and country exposure, and trailing returns. Returns 410 Gone when the symbol is flagged as delisted_candidate by the upstream cycle. Since DATA-N4.4 the canonical snapshot is rebuilt purely from Tier S sources (regulated-exchange price + SEC NPORT-P holdings), with no commercial aggregator in the chain. Fields awaiting their replacement source are returned as ``null`` and tagged in the internal ``_sources.deferred`` map: ``nav``/``aum_usd``/``premium_discount_pct`` (DATA-N4.3), ``returns_*`` and ``fifty_two_week_high``/``fifty_two_week_low`` (DATA-N4.1), and ``expense_ratio_pct``/``yield_dividend_pct``/``yield_distribution_pct``/``inception_date`` (DATA-N4.2). DATA-N4.8.1: when ``price`` is null but a NAV is available, an additive ``price_proxy`` block surfaces the NAV as an explicitly-stale proxy (``basis = nav`` with an ``as_of`` SEC-filing date that can be months old and a ``note`` disclaiming a current quote). ``price`` itself stays null - the proxy is never presented as a live quote. The block is absent when ``price`` is present or when ``nav`` is also null. ## Path parameters - `symbol` string, required — ETF ticker. ## Query parameters - `date` string, nullable — Optional snapshot date (YYYY-MM-DD). Defaults to the latest cycle. ## Response `200` Latest or dated ETF snapshot payload. - EnvelopeEtfSnapshotPayload - `data` EtfSnapshotPayload, required — Full per-symbol snapshot payload. - `symbol` string, required — ETF ticker. - `name` string, nullable — Fund full name. - `category` string, nullable — Fund category. - `snapshot_date` string, required — Logical snapshot date (ISO). - `snapshot_taken_at` string, nullable — ISO timestamp at upstream fetch time. - `manifest_version` string, nullable — Manifest version that produced this snapshot (Unix timestamp). - `nav` number, nullable — Net Asset Value. Since DATA-N4.3 sourced from SEC data: re-based from NPORT-P net assets over the audited 485BPOS share count (``_sources.nav.method = monthly_derived``) when available, else the annual audited 485BPOS NAV (``annual_485bpos``). Null only when the prospectus input is missing for this ETF. - `price` number, nullable — Regular-session previous close (regulated exchange). - `price_proxy` PriceProxy — DATA-N4.8.1 additive NAV price-proxy block. Surfaced ONLY when the snapshot has no exchange price (``price`` is null) but a SEC-derived NAV is available. The NAV is offered as an explicitly-stale reference value - never as a current quote. The ``price`` field itself stays null, so a client keying on ``price`` sees absence, not a fabricated number. Absent when ``price`` is present or when ``nav`` is also null. - `value` number, nullable — The NAV value used as the price proxy (equals the snapshot ``nav``). - `basis` string, required — Always ``nav`` - signals this is a NAV proxy, not a live quote. - `as_of` string, nullable — ISO date the NAV was sourced (the SEC filing date). Period-stale by construction - can be months old. Null when provenance is unavailable. - `method` string, nullable — NAV derivation method from ``_sources.nav.method`` (``monthly_derived`` from NPORT-P net assets, else ``annual_485bpos`` for the audited prospectus NAV). Null when provenance is unavailable. - `note` string, nullable — Honest staleness disclaimer - the proxy is not a current quote. - `premium_discount_pct` number, nullable — (price - nav) / nav * 100. Since DATA-N4.3 the NAV basis is period-stale (SEC-filing as-of, not same-day); see ``_sources.premium_discount_pct.note``. Null when nav or price is null, and ALWAYS null for the Leveraged Equity / Inverse Equity universe categories (API-1.14.3: every available NAV basis is period-stale against a daily-reset geared fund, so the figure would read as a fabricated premium; see ``_sources.deferred.premium_discount_pct``). - `fifty_two_week_high` number, nullable — Deferred (DATA-N4.1) - null pending exchange quote history. - `fifty_two_week_low` number, nullable — Deferred (DATA-N4.1) - null pending exchange quote history. - `aum_usd` number, nullable — Total assets under management in USD. Since DATA-N4.3 sourced from SEC NPORT-P fund-level net assets (exact) or, as a fallback, the 485BPOS audited net assets. Null only when both inputs are missing for this ETF. - `expense_ratio_pct` number, nullable — Annual report expense ratio as percent. Since DATA-N4.2 sourced from the SEC 485BPOS Financial Highlights. - `yield_dividend_pct` number, nullable — Dividend yield as percent. Since DATA-N4.2 proxied from the SEC 485BPOS net-investment-income ratio (equal to ``yield_distribution_pct`` in v1; see ``_sources``). - `yield_distribution_pct` number, nullable — Distribution yield as percent. Since DATA-N4.2 proxied from the SEC 485BPOS net-investment-income ratio. - `inception_date` string, nullable — ISO inception date. Since DATA-N4.2 sourced from the SEC N-1A prospectus body ('commenced operations on ...'). - `top_holdings` ModelsEtfHolding[], nullable — Top-10 holdings sample. - `symbol` string, nullable — Ticker of the held position (null for cash, futures, bonds). - `name` string, required — Issuer name. - `weight_pct` number, required — Portfolio weight as percentage (0.0-100.0). - `sector` string, nullable — Canonical Sugra sector or null. - `asset_class` string, nullable — High-level asset class (equity, bond, cash, other). - `sector_yahoo_raw` SectorWeightRaw[], nullable — Raw sector weight rows as stored on the snapshot blob. Wire field name is historical; prefer ``sector_canonical`` for consumers. - `label` string, required — Raw sector label as returned by upstream. - `weight_pct` number, required — Weight as percentage. - `sector_canonical` SectorWeightCanonical[], nullable - `sector` string, required — Canonical Sugra sector slug. - `weight_pct` number, required — Weight as percentage. - `asset_class_weightings` AssetClassWeightings — Asset-class breakdown for the snapshot. - `equity_pct` number, nullable — Equity percentage. - `bond_pct` number, nullable — Bond percentage. - `cash_pct` number, nullable — Cash percentage. - `other_pct` number, nullable — Other (commodities, derivatives) percentage. - `country_weightings` ModelsEtfCountryWeight[], nullable - `country_code` string, required — ISO 3166-1 alpha-2 country code. - `weight_pct` number, required — Country weight in percent. - `returns_1m` number, nullable - `returns_ytd` number, nullable - `returns_1y` number, nullable - `returns_3y` number, nullable - `returns_5y` number, nullable - `returns_10y` number, nullable - `data_source` string, nullable — Upstream data-source identifier for the PRICE + HOLDINGS origin. Since DATA-N4.4 the canonical snapshot is rebuilt from Tier S sources: exchange quotes plus SEC N-PORT when both contributed, exchange quotes alone (SEC blob absent, e.g. a commodity-pool ETF) or SEC N-PORT alone (exchange-quote blob absent). The SEC 485BPOS prospectus (DATA-N4.3 + N4.2) additionally supplies NAV / AUM / expense ratio / yields / inception; its per-field provenance lives in ``_sources`` (the top-level slug intentionally still reflects only price + holdings). Legacy blobs may still carry a retired commercial fund-summary token from DATA-N1. - `license_attribution` string, nullable — License attribution string. - `_sources` object, nullable — DATA-N4.4 per-field provenance (internal metadata, additive). Maps each populated field to its Tier S source. Price carries the exchange ``as_of``; holdings/weightings carry SEC NPORT-P ``rep_pd_date`` + ``accession``. Since DATA-N4.3 + N4.2 the seven fields ``nav``/``aum_usd``/``premium_discount_pct`` and ``expense_ratio_pct``/``yield_dividend_pct``/``yield_distribution_pct``/``inception_date`` are POPULATED from SEC data and carry their own ``_sources`` entry: ``nav`` records ``method`` (``monthly_derived`` when re-based from NPORT-P net assets, else ``annual_485bpos`` for the audited prospectus NAV) + ``as_of``; ``premium_discount_pct`` records ``nav_method`` / ``nav_as_of`` / ``price_as_of`` plus a ``note`` that the NAV basis is period-stale (absent for the Leveraged Equity / Inverse Equity categories, where the field is deferred under an API-1.14.3 tag and ``nav.drift_warning`` may carry reason ``leveraged_or_inverse``). The ``deferred`` map now carries only the DATA-N4.1 fields (``returns_*`` + ``fifty_two_week_high``/``fifty_two_week_low``) at baseline; any of the seven SEC-sourced fields is re-added to ``deferred`` per-symbol ONLY when its prospectus / NPORT-P input was missing for that ETF. - `meta` SugraMeta, required — Metadata on a /api/v1/* response envelope built through `helpers.response.sugra_response`, which is how routes are expected to answer. A route that assembles its own `meta` dict carries only the keys it writes itself, so an optional field below can be absent because this response has nothing to report OR because that route does not build its envelope here - the two are not distinguishable from the outside (API-43). - `endpoint` string, required — Requested endpoint path. - `data_time` string, required — ISO 8601 timestamp the data on this response is stamped with. It is the source's own timestamp whenever the source supplied one this API could read; when it did not, this field falls back to the value of `response_time` and `data_age_days` is omitted, so the PRESENCE of that field is the signal to read - with the one exception named in its own description, a route that substitutes its own current time for a source timestamp it never received. Usually UTC (`Z`), but a source stating its own numeric offset keeps it (2026-04-16T14:30:00+09:00) rather than being converted a second time. For a source that publishes by period this is the period's START (see `period`) and for one that publishes by calendar day it is that day's midnight - in neither case a moment at which anything was observed or released. - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced. - `provider` string, required — API name and version. - `data_age_days` number, nullable — Age of the data in days at the moment this response was produced, i.e. `response_time` minus `data_time`. Present ONLY when the timestamp this response is stamped with is a clock time that could be read as a real instant. It is ABSENT - never 0 - in every other case. Absent when no readable source timestamp was supplied, because `data_time` then repeats `response_time` and a zero age would assert that the data is current precisely where its true age is unknown. Absent when the source names a calendar day, a month, a quarter or a year (see `period`): the instant is then a boundary this API anchored at midnight, and time since a day or a quarter BEGAN is a different quantity from the age of the data - a daily series is out by up to a day, a quarterly one by up to a quarter. A midnight counts as such a boundary whichever zone it is stated in, and whether the source stated it or this API anchored it. The one case this field cannot see is a route that substitutes its own current time for a source timestamp it never received: the substituted value is a real, readable instant and is indistinguishable from one the source stated, so the age reads as roughly 0. The shared cache-and-fetch helper behind most routes stopped doing that (API-43), but the presence of this field is a statement about the timestamp the response carries, not a guarantee about the route that supplied it. Rounded to 0.001 day (86.4 seconds), so 0.0 is a real measured age anywhere within roughly +/-43 seconds and not a stand-in for unknown; a source stamping an instant in the future reports a negative value (-0.001 or less) rather than being clamped. Sources publish on very different cadences, so a non-zero age is normal, not an error. Preserve absence in client code: a generated client that materialises a missing optional number as its numeric default turns 'age unknown' back into 'age zero', which is the exact confusion this field exists to remove. - `source` string, nullable — Identifier of the primary upstream source used for this response. - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response. - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data. - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried. - `cached` boolean, nullable — True when this response was served from the internal cache. - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data. - `period` string, nullable — Unit of observation, when the source publishes by period rather than by instant. `data_time` carries the period's START instant so it stays machine-readable; this field preserves what that instant used to mean, which the conversion would otherwise erase. Present only for such sources, and only when the source hands the API the label itself - a client that converts the period to its start instant before building the envelope loses the label, though not the age exclusion, which is decided by the instant. Note that `data_age_days` is omitted whenever this is present, because an age measured from a period start is not a freshness figure. - `notes` string, nullable — Data-quality caveat about THIS response - how old the underlying report is, a chokepoint AIS lower-bound, or that a source-reported `data_time` could not be read and the response time is shown instead. Distinct from `attribution`, which is a licensing obligation. Multiple caveats are joined with ' | '. Present only when there is one. ## Other responses - `401` — Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401. - `422` — Validation Error - `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window. - `503` — Upstream source is temporarily unavailable. Retry after a short delay. ## Changes - **2026-09-01** `328d061c12ca` — 3 info - added the optional property `meta/data_age_days` to the response with the `200` status - added the optional property `meta/notes` to the response with the `200` status - added the optional property `meta/period` to the response with the `200` status - **2026-08-08** `4c4530760ba1` — 12 info - added the optional property `code` to the response with the `401` status - added the optional property `code` to the response with the `429` status - added the optional property `code` to the response with the `503` status - added the optional property `hint` to the response with the `401` status - …8 more [Change history](https://skmtc.dev/sugra/apis/sugra-api/changes/api/v1/etf/:symbol/snapshot/get.md) --- [API](https://skmtc.dev/sugra/apis/sugra-api.md) · [All operations](https://skmtc.dev/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sugra/sugra-api/revisions/cdcc60731935/schema)