---
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`

## Request

- Base URL: `https://api.0xinsider.com`
- URL: `https://api.0xinsider.com/api/v1/market/{condition_id}/snapshot`
- Auth: one of:
  - HTTP bearer
  - OAuth 2
    - Authorization code: `https://0xinsider.com/oauth/authorize`
    - Token URL: `https://api.0xinsider.com/oauth/token` scopes: `read`
- TypeScript: <https://skmtc.dev/0xinsider/apis/0xinsider-api/docs/api/v1/market/:condition_id/snapshot/get.ts> (a function with typed inputs; its response is checked against the schema)

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

- `X-Query-Validation` 'strict'
- `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, required
      - `slug` string, nullable, required
      - `page_slug` string, nullable, required
      - `event_slug` string, nullable, required
      - `category` string, nullable, required
      - `status` 'active' | 'closed', required
      - `description` string, nullable, required
      - `image` string, nullable, required
      - `series_slug` string, nullable, required: Polymarket series slug from the canonical identity row, null when unavailable. A sports series identifies a league and must not be used as a per-matchup grouping key.
      - `market_type` string, nullable, required
      - `market_result` string, nullable, required
      - `created_at` string, date-time, nullable, required
      - `end_date` string, date-time, nullable, required
      - `resolved_at` string, date-time, nullable, required
    - `outcomes` object[], required
      - `side` 'yes' | 'no', required
      - `label` string, required
      - `token_id` string
      - `current_price` number
      - `top_of_book` MarketSnapshotTopOfBook, required
        - `status` 'available' | 'unavailable', required
        - `source` string, required
        - `best_bid` number
        - `best_ask` number
        - `spread_bps` integer
        - `bid_depth_usdc` number
        - `ask_depth_usdc` number
        - `reason` string
    - `liquidity` object, required
      - `source` string, required
      - `volume_usd` number, nullable, required
      - `liquidity_usd` number, nullable, required
      - `volume_24h_usd` number, nullable, required
      - `last_price` number, nullable, required: Always null. Polymarket snapshot prices come from outcome top-of-book midpoints.
    - `sports` object, required
      - `status` 'fresh' | 'stale' | 'not_live' | 'unavailable', required
      - `source` string, required
      - `live_match_key` string
      - `live_league_key` string
      - `live_score` object: Live-score period and elapsed may be omitted when unavailable (older responses use null). A score entry may omit full_name when it equals team; fall back to team. Distinct aliases and score admission markers are preserved.
      - `reason` string
    - `freshness` object, required
      - `market_data` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time
        - `stale_after_s` integer: Age-relative freshness bound when known. Omitted for live_sports: its as_of records compute start, while its two-second freshness marker starts at publication.
        - `reason` string
      - `top_of_book` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time
        - `stale_after_s` integer: Age-relative freshness bound when known. Omitted for live_sports: its as_of records compute start, while its two-second freshness marker starts at publication.
        - `reason` string
      - `live_sports` MarketSnapshotFreshness, required
        - `status` 'fresh' | 'stale' | 'available' | 'not_live' | 'unavailable', required
        - `source` string, required
        - `as_of` string, date-time
        - `stale_after_s` integer: Age-relative freshness bound when known. Omitted for live_sports: its as_of records compute start, while its two-second freshness marker starts at publication.
        - `reason` string
    - `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: 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
          - `max_age_s` integer
        - `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
        - `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
      - `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: 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
          - `max_age_s` integer
        - `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
        - `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
  - `meta` ResponseMeta, required
    - `request_id` string, required: Unique request ID (req_ prefix). The same value as the X-Request-Id response header, the request's usage accounting row and its log lines.
    - `cached` boolean, required
    - `cache_age_s` integer: 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.
    - `ranking_generation` integer: Committed PostgreSQL-owned leaderboard generation for the returned rows and cursor. Present on GET /api/v1/leaderboard; omitted on endpoints that do not read this ranking.
    - `ranking_as_of` string, date-time: Authoritative RFC3339 timestamp from cache_generations.updated_at for ranking_generation. It is read in the same repeatable-read snapshot as the leaderboard rows and is not request time, cache write time, or row insertion order.
    - `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 sharp-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 sharp-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' | 'graded_wallet_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. The key is valid but the account has no active Pro subscription; error.reason is subscription_inactive and error.message names the reactivation URL (https://0xinsider.com/billing). Permanent until a person reactivates: no Retry-After, never retry on a schedule.
- `403`: Account access denied
- `404`: Resource not found
- `408`: The handler did not answer inside the server's 30-second timeout. error.code is request_timeout. On GET and HEAD the response carries Retry-After and error.retry_at; on a mutation it carries neither, because the request may have completed on the server: check its state before repeating it, and reuse its Idempotency-Key.
- `423`: Account is locked
- `429`: Rate limit exceeded. Three 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 plus RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset before any item work is done. (3) The monthly quota: Pro includes 250,000 authenticated requests per UTC calendar month, whatever the billing cadence. Over 250,000: with pay as you go on, requests keep answering and the excess bills at USD 0.20 per 1,000 on a monthly invoice, up to 1,000,000 requests a month; without it, from October 1, 2026, the next request answers 429 rate_limited with error.reason monthly_quota_exceeded and a Retry-After to the month's reset, and from the same day a pay-as-you-go account answers the same past 1,000,000. A refused request is not counted. Every authenticated response carries X-Monthly-Quota-Limit, X-Monthly-Quota-Remaining, and X-Monthly-Quota-Reset (unix seconds, the first of next month). (4) The per-address budget: 1200 requests/minute per IP, shared by every caller behind one address and counted before authentication, on every route. A 429 from it carries error.reason ip_rate_limited and describes that bucket in RateLimit-*; a throttled address (sustained over-limit traffic) carries error.reason ip_throttled with a Retry-After of minutes to days, and a request before it does not shorten the cooldown. Every 429 is the standard error envelope with meta.request_id equal to X-Request-Id.
- `503`: Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown

## Changes

- **2026-09-23** `ece7a25b7a44`: 9 warning, 9 info
  - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `400`
  - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `401`
  - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `402`
  - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `403`
  - …14 more
- **2026-09-23** `8462acf80f8c`: 9 warning
  - added the new `export_expired` enum value to the `error/reason` response property for the response status `400`
  - added the new `export_expired` enum value to the `error/reason` response property for the response status `401`
  - added the new `export_expired` enum value to the `error/reason` response property for the response status `402`
  - added the new `export_expired` enum value to the `error/reason` response property for the response status `403`
  - …5 more
- …earlier changes not shown

[Operation history](https://skmtc.dev/0xinsider/apis/0xinsider-api/changes/api/v1/market/:condition_id/snapshot/get.md)

---

[API](https://skmtc.dev/0xinsider/apis/0xinsider-api.md) - [All operations](https://skmtc.dev/0xinsider/apis/0xinsider-api/llms.txt) - [OpenAPI document](https://skmtc.dev/0xinsider/apis/0xinsider-api/revisions/2035b3316329?raw)