---
title: "Get market live snapshot"
method: GET
path: "/api/v1/market/{condition_id}/snapshot"
tags: ["Markets"]
---

# Get market live snapshot

`GET /api/v1/market/{condition_id}/snapshot`

Provider-first market card snapshot with canonical identity, outcome labels, cached top-of-book when available, liquidity, live sports context, and explicit freshness/unavailable states.

## Path parameters

- `condition_id` string, required

## Query parameters

- `expand[]` string[]
- `expand` string[]

## Headers

- `If-None-Match` string

## Response `200`

Provider-first market snapshot

- object
  - `object` 'market_snapshot', required
  - `data` MarketSnapshot, required
    - `market` object, required
      - `id` string, required
      - `condition_id` string, required
      - `provider` string, required
      - `title` string, nullable
      - `slug` string, nullable
      - `page_slug` string, nullable
      - `event_slug` string, nullable
      - `category` string, nullable
      - `status` 'active' | 'closed', required
      - `description` string, nullable
      - `image` string, nullable
      - `series_slug` string, nullable — Series slug from the canonical identity row. Null for Kalshi markets, which carry their series in kalshi_series_slug. For other providers, which today means Polymarket, it is populated only when the canonical row carries a provider seriesSlug, and null otherwise -- so treat null as ordinary, not as a fault. Measured 2026-08-02: non-null on 44,103 of 2,022,671 Polymarket rows lifetime, and on 37,654 of 47,832 rows refreshed in the previous 24 hours. NOTE the granularity for Polymarket: a seriesSlug is a LEAGUE, not a single series -- every same-day MLB game carries mlb -- so it is not a per-matchup grouping key, and the backend itself refuses it as one (#8124). Additive change (#8134): this field was previously null on every market, because its former source column had no working writer.
      - `kalshi_series_slug` string, nullable — Kalshi series slug, served from the markets mirror. Null is ORDINARY, not a fault: measured 2026-08-02, non-null on 10,778 of 69,866 Kalshi rows, so most Kalshi markets have none here. One legacy row on the polymarket platform also carries a value. The canonical column holds the ticker for more Kalshi rows, but this field deliberately keeps reading the mirror; changing that is a separate wire change.
      - `market_type` string, nullable
      - `market_result` string, nullable
      - `created_at` string, date-time, nullable
      - `end_date` string, date-time, nullable
      - `resolved_at` string, date-time, nullable
    - `outcomes` object[], required
      - `side` 'yes' | 'no', required
      - `label` string, required
      - `token_id` string, nullable
      - `current_price` number, nullable
      - `top_of_book` MarketSnapshotTopOfBook, required
        - `status` 'available' | 'unavailable', required
        - `source` string, required
        - `best_bid` number, nullable
        - `best_ask` number, nullable
        - `spread_bps` integer, nullable
        - `bid_depth_usdc` number, nullable
        - `ask_depth_usdc` number, nullable
        - `reason` string, nullable
    - `liquidity` object, required
      - `source` string, required
      - `volume_usd` number, nullable
      - `liquidity_usd` number, nullable
      - `volume_24h_usd` number, nullable
      - `last_price` number, nullable — Last traded price from the provider metadata sync. Kalshi only; always null for Polymarket markets (live Polymarket prices come from the price endpoints, not this snapshot).
    - `sports` object, required
      - `status` 'fresh' | 'stale' | 'not_live' | 'unavailable', required
      - `source` string, required
      - `live_match_key` string, nullable
      - `live_league_key` string, nullable
      - `live_score` object, nullable
      - `reason` string, nullable
    - `freshness` object, required
      - `market_data` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time, nullable
        - `stale_after_s` integer, nullable
        - `reason` string, nullable
      - `top_of_book` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time, nullable
        - `stale_after_s` integer, nullable
        - `reason` string, nullable
      - `live_sports` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time, nullable
        - `stale_after_s` integer, nullable
        - `reason` string, nullable
    - `trust` MarketSnapshotTrust — Price and spread trust metadata returned only when GET /api/v1/market/{condition_id}/snapshot includes expand=trust.
      - `current_price` TrustMetadata, required — Shared source/freshness/reconciliation/completeness metadata for public API values that may be cached, stale, partial, computed, or provider-unavailable. Unavailable provider values must be represented with explicit metadata instead of fabricated zeros or empty arrays.
        - `source` TrustSource, required — Source metadata for a trust-critical value. Providers and DB/read models own business truth; clients should not infer missing provider facts from titles, slugs, zeros, or empty arrays.
          - `kind` 'provider' | 'database' | 'cache' | 'computed' | 'client_input' | 'unavailable', required
          - `owner` string, required — Provider, table/read-model, cache, or service that owns the value.
          - `field` string, nullable — Provider field, DB column, or computed field name when applicable.
        - `freshness` TrustFreshness, required — Freshness metadata for a trust-critical value. This is separate from transport cache fields in ResponseMeta.
          - `status` 'fresh' | 'refreshing' | 'stale' | 'not_live' | 'unknown' | 'unavailable', required
          - `as_of` string, date-time, nullable
          - `max_age_s` integer, nullable
        - `reconciliation` TrustReconciliation, required — How provider-owned facts were reconciled with stored/read-model values.
          - `status` 'provider_backed' | 'db_mirror' | 'computed' | 'partial' | 'not_applicable' | 'unavailable', required
          - `detail` string, nullable
        - `completeness` TrustCompleteness, required — Whether the described value or result set is complete for its stated contract.
          - `status` 'complete' | 'partial' | 'not_computed' | 'not_applicable' | 'unavailable', required
          - `detail` string, nullable
      - `spread_bps` TrustMetadata, required — Shared source/freshness/reconciliation/completeness metadata for public API values that may be cached, stale, partial, computed, or provider-unavailable. Unavailable provider values must be represented with explicit metadata instead of fabricated zeros or empty arrays.
        - `source` TrustSource, required — Source metadata for a trust-critical value. Providers and DB/read models own business truth; clients should not infer missing provider facts from titles, slugs, zeros, or empty arrays.
          - `kind` 'provider' | 'database' | 'cache' | 'computed' | 'client_input' | 'unavailable', required
          - `owner` string, required — Provider, table/read-model, cache, or service that owns the value.
          - `field` string, nullable — Provider field, DB column, or computed field name when applicable.
        - `freshness` TrustFreshness, required — Freshness metadata for a trust-critical value. This is separate from transport cache fields in ResponseMeta.
          - `status` 'fresh' | 'refreshing' | 'stale' | 'not_live' | 'unknown' | 'unavailable', required
          - `as_of` string, date-time, nullable
          - `max_age_s` integer, nullable
        - `reconciliation` TrustReconciliation, required — How provider-owned facts were reconciled with stored/read-model values.
          - `status` 'provider_backed' | 'db_mirror' | 'computed' | 'partial' | 'not_applicable' | 'unavailable', required
          - `detail` string, nullable
        - `completeness` TrustCompleteness, required — Whether the described value or result set is complete for its stated contract.
          - `status` 'complete' | 'partial' | 'not_computed' | 'not_applicable' | 'unavailable', required
          - `detail` string, nullable
  - `meta` ResponseMeta, required
    - `request_id` string, required — Unique request ID (req_ prefix).
    - `cached` boolean, required
    - `cache_age_s` integer, nullable — Cache age in seconds. Omitted when the response was not cached, and also when it was cached but its age cannot be established (an entry stored before its cache carried a computed instant). Never a placeholder: an unknown age is reported as no value rather than as the cache TTL.
    - `cost` integer, required — Advisory request weight (relative compute cost). 1 for simple reads; higher for heavier endpoints. Not a credit/price.
    - `directional_source` 'live' | 'degraded' — Which path produced the team-directional read on this response. Only present on endpoints that compute one (today: GET /api/v1/sports-edge-signals). "live" means the read RAN. "degraded" means it FAILED, so nothing was measured and the ranking fell back to raw conviction. The flag describes the READ, not its consequence: a read that ran and found nothing groupable also leaves the directional fields null, and that is honestly "live" -- the per-signal nulls already say "nothing to enrich here", so this snapshot-level flag carries only what they cannot, namely whether the read ran at all. A degraded response is cached on the shorter degraded TTL so it self-heals. Reported SEPARATELY from ranking_source because the two degradations are independent -- a smart-money DB miss weakens the ranking DATA, a directional failure removes a ranking WEIGHT -- and a consumer down-weighting a degraded response needs to know which input it lost. Omitted on endpoints that compute no directional read.
    - `ranking_source` 'live' | 'db_only' — Which ranking-data path produced this response. Only present on endpoints that can degrade a ranking (today: GET /api/v1/sports-edge-signals). "live" is the normal path (the current holder pile from the provider batch); "db_only" is the degraded fallback (a truthful but weaker trader_markets ranking) served when the live sharp-money ranking batch is unavailable (a smart-money DB read failure, not a Polymarket outage) and cached on a shorter TTL, so a consumer can down-weight or skip it. Omitted on endpoints that never degrade.
    - `category_skill_source` 'live' | 'partial' | 'degraded' | 'unavailable' — Whole filtered snapshot category-evidence status before pagination. Operational live always remains partial source coverage.
    - `category_skill_model_version` string
    - `category_skill_taxonomy_version` string
    - `category_skill_platform` 'polymarket'
    - `category_skill_scope` 'observed_goldsky_primary_taker_fill'
    - `category_skill_source_coverage` 'partial_whale_threshold_fills'
    - `category_skill_observation_started_at` string, date-time
    - `category_skill_model_operationally_degraded` boolean — Whole-model operational readiness captured with the category model snapshot. Present on category-enriched responses even when the filtered signal list is empty. When true, category_skill_source is degraded and sports-edge-signals uses the shorter degraded cache TTL.
    - `category_skill_status_counts` object
      - `live` integer, required
      - `insufficient` integer, required
      - `stale` integer, required
      - `unknown` integer, required
      - `degraded` integer, required
    - `category_skill_base_payload_hash` string — SHA-256 of the funded signal membership/order/rank/cursor vector immediately before category-skill enrichment. Sports-edge-signals only.
    - `category_skill_enriched_base_payload_hash` string — Independent SHA-256 recomputation over the same base fields immediately after category-skill enrichment. Equality with category_skill_base_payload_hash proves shadow enrichment did not change funded inputs. Sports-edge-signals only.

## Other responses

- `304` — Not Modified. Returned when If-None-Match matches the current payload.
- `400` — Invalid request parameter
- `401` — Missing or invalid API key
- `402` — Active Pro subscription required
- `403` — Account access denied
- `404` — Resource not found
- `408` — Request exceeded the server's 30-second transport timeout. The timeout response has an empty body because it is generated before handler-level JSON error shaping.
- `423` — Account is locked
- `429` — Rate limit exceeded. Two independent budgets. (1) 100 requests/minute per user (sliding window), on every authenticated route. (2) On the BATCH routes only: 2500 batch item units/minute per user, reserved before any item is executed. A batch with N requested items costs N item units, including duplicate and invalid items. 2500 = 100 requests x 25 items per batch, which is the most item work a key can buy through the request limiter at all: a caller may spend their entire 100-request minute on full 25-item batches without the item budget being what stops them. The REQUEST budget is the effective ceiling, and batching is never the more expensive choice. The item budget can still deny at a sliding-window boundary (both counters carry the previous window forward with a floor, and the item counter runs 25x the request counter), so honor a 429 from either. Over-quota batches return 429 with Retry-After before any item work is done.
- `503` — Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown

---

[API](https://skmtc.net/0xinsider/apis/0xinsider-api.md) · [All operations](https://skmtc.net/0xinsider/apis/0xinsider-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/0xinsider/0xinsider-api/revisions/be0e25f93c7d/schema)