Markets

Resolve venue-specific identifiers to canonical Kairos market ids

Maps up to 200 venue-specific identifiers — market-scoped (a venue's market id, ticker, or condition-like identifier) or outcome-scoped (an outcome/token id) — onto Kairos's canonical market_id for that provider. Requests are grouped by (provider, scope) for efficient batch resolution. Not cached (Cache-Control: no-store).

Rate-limit bucket: LIGHT, but with a distinct cost model from the other batch endpoints — the request is admitted at a base cost of 1 unit, then the service charges the FULL request-item count (len(requests) - 1 additional units) as a deferred charge immediately after the body is parsed and size-validated, before any per-item validation runs. This means a batch of N requests always costs N light units even if individual items subsequently fail validation (e.g. a bad scope) and the call returns 400.

Unresolved identifiers are reported with found: false and market_id: null rather than causing the whole call to fail.

Id spaces. scope: market matches the venue's market identity — a Kalshi ticker, a Polymarket Gamma numeric market id, or a 0x… condition id. scope: outcome matches an on-chain outcome/token id only (the decimal ERC1155 string), never a market id; submitting a market id with scope: outcome returns found: false. Resolution always returns the canonical market_id; it never returns outcome token ids. To go from a market discovered via the Data API's /search/markets to its outcome tokens, read token_ids/outcomes on the search result (or call the Data API's POST /markets/details), then feed those token ids to /v1/synthetics and /v1/candles.

The request body is capped at 1 MiB.

post/v1/market-identifiers/resolve

Request

  • Base URL
    https://md.kairos.trade
  • Auth
    • none
    • or API key in header X-Client-Id and API key in header X-Api-Key and API key in header X-Api-Secret

Request body

Example request

{
  "requests": [
    {
      "identifier": "18812649149814341758733697580460697418474693998558159483117"
    }
  ]
}

Response

Per-item resolution results, in request order.

Example response

{
  "results": [
    {
      "provider": "kalshi_offchain"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.