---
title: "Resolve ambiguous ticker query to canonical symbol"
method: GET
path: "/api/v2/quotes/resolve"
tags: ["Finance"]
---

# Resolve ambiguous ticker query to canonical symbol

`GET /api/v2/quotes/resolve`

Disambiguates ticker queries against a Blob-cached static map of 30+ primary-source publishers (Wikidata + OpenFIGI + per-exchange CSVs) rebuilt biweekly by sugra-ingest. Falls back to upstream /search with name cross-validation for queries the static map does not cover. Use `?strict=true` to skip the upstream fallback (deterministic mode for AI agents).

## Query parameters

- `q` string, required — Ticker symbol (e.g. `BABA`, `9988`, `7203`, `9988.HK`) or company name (`Alibaba`).
- `strict` boolean — When true, return 404 if the static map has no entry (skip upstream /search fallback).

## Response `200`

Canonical Sugra Finance symbol plus exchange / company metadata.

- EnvelopeResolveResponseV2
  - `data` ResolveResponseV2, required
    - `symbol` string, required — Canonical Sugra Finance ticker symbol (e.g., AAPL, 9988.HK, 7203.T).
    - `exchange` string, nullable — Exchange code (NYQ, NASDAQ, HKG, JPX, KSC, etc.).
    - `name` string, nullable — Company / security display name.
    - `confidence` 'high' | 'medium', required — Resolution confidence - `high`: 2+ primary sources agree on the listing, `medium`: single source (typical Sprint 1 baseline) or upstream /search with `/quoteType` cross-validation. The endpoint never returns unverified results, so `low` is not a possible value.
    - `source` string, required — Where the resolution came from: `static_map` | `static_name_index` | `search_verified` | `alias_redirect`. `static_name_index` (Sprint 11) is set when the resolver matched a multi-word company-name query against the prebuilt name index instead of a ticker lookup.
    - `primary_listing` string, nullable — Symbol of the primary listing if `symbol` is an ADR / cross-listing.
    - `us_default` boolean — True when this is the US-default resolution for a bare ticker (e.g., BABA -> NYSE ADR).
    - `alternatives` string[] — Cross-listings (different exchange) of the same security. Empty when the security trades only on one exchange.
    - `share_class_siblings` string[] — Same-exchange share-class peers (e.g. `BRK-B` for `BRK-A`; `GOOG` for `GOOGL`). Empty when the security has no dual-class structure.
    - `company_id` string, nullable — Wikidata Q-ID of the underlying company.
    - `figi` string, nullable — OpenFIGI composite FIGI for the security, when known.
    - `sources` string[] — Source providers that agreed on this resolution (`wikidata`, `openfigi`, `nasdaq_csv`, `hkex_csv`, …).
    - `status` 'active' | 'delisted' — Sprint 10: trading status. `active` = ticker currently trades. `delisted` = at least one signal flagged the listing as no longer trading. Defaults to `active` for blob entries that pre-date the Sprint 10 schema.
    - `delisting_signals` string[] — Source labels that fired the delisted status. `wikidata_p582` = Wikidata curator marked the listing with an end-time qualifier on the canonical's PRIMARY listing (Sprint 10.x.3 narrowed scope from any cross-listing to primary-only - non-primary historical delistings no longer poison status). `sec_absent` = ticker missing from SEC `company_tickers.json` while Wikidata corroborated US-listing. `sec_form25` (Sprint 10.x.7 RE-ENABLED) = SEC daily-index recorded a Form 25 / 25-NSE deregistration for this US bare ticker in the last 30 business days, with per-filing content classification confirming the affected security is common equity (not corporate debt notes / preferred / warrants / depositary-of-preferred). Stronger and ~13 days earlier label than `sec_absent` for the equity case. Empty when status is active.
    - `delisting_end_date` string, nullable — ISO date string. Populated when any time-bearing signal fires: `wikidata_p582` (P582 end-time qualifier) or `sec_form25` (Form 25 filing date). Most recent date wins when multiple signals carry dates.
    - `relisted_at` string, nullable — Sprint 10.x.1: ISO date when SEC daily-index recorded a Form 8-A12B / 8-A12G filing (registration of a new class of securities) for this US bare ticker, AND the listing previously had a Wikidata P582 end-time stamp on its primary listing. Populated only on canonicals where Wikidata previously marked the primary listing as ended; this gate excludes first-time IPOs, uplistings, and new share class registrations from being flagged as relistings. Null when no recent relisting filing exists or no prior P582 evidence supports the relisting interpretation.
    - `listing_date` string, nullable — Sprint 11: ISO date when the security was first listed on its primary exchange. NSE provides this for Indian equities; null otherwise.
    - `series` string, nullable — Sprint 11: NSE trading-series code (`EQ` = cash equity, `BE` = trade-to-trade, `BL` = bulk). Null for non-NSE listings.
    - `group` string, nullable — Sprint 11: BSE trading-group classification (`A`/`B`/`T`). Null for non-BSE listings.
  - `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/v2/quotes/resolve/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/85caa556892f/schema)