> ## Documentation Index > Fetch the complete documentation index at: https://docs.kairos.trade/llms.txt > Use this file to discover all available pages before exploring further. # List sports fixtures with live status and win probabilities > Fixture board backed by the TxODDS score event store. Kick-off bounds are snapped to the minute — `from_ms` rounds down and `to_ms` rounds up, so the window may extend up to 59s past what was asked for. Per-row status is computed at cache time from feed phase plus wall clock, so a live-status flip can lag by up to one cache TTL. Concurrent misses on the same page share a single build. ## OpenAPI ````yaml /openapi/data-api.yaml get /txodds/fixtures openapi: 3.1.0 info: title: Kairos Data API version: 1.0.0 summary: >- The full Kairos data plane — markets, candles, trades, search, discover, sports, trader analytics, and PnL. description: | The Kairos Data API at `data.kairos.trade` is the platform's primary data plane: market metadata and prices, OHLCV candles, live venue trade proxies, normalized trade history, full-text search, discovery feeds, the sports catalog, public trader analytics, and account PnL. ## Authentication Most endpoints accept a Kairos **API key** (`X-Client-Id` + `X-Api-Key` + `X-Api-Secret`, all three) or a first-party session JWT. Endpoints tagged `public` (trader analytics, provider configs, several sports feeds) need no credentials at all. Some endpoints additionally require an API-key **scope** (`trade:read`, `position:read`) — stated per operation. For high-volume market-data consumption (candles/trades/metadata at scale), prefer the dedicated **Market Data API** at `md.kairos.trade` — it has higher budgets, ETag caching, and a binary candle format. ## Rate limits Rate limits use a sliding window keyed on the authenticated user (JWT `sub`) or, for anonymous callers, the trusted client IP. Routes belong to a named **bucket** (`x-kairos-bucket`) whose per-minute budget is shared by every route in it; routes with no bucket run under the service default of 100/minute. `x-kairos-rate-limit` states the bucket's compile-time default — operators can raise or lower a bucket at runtime, so treat the documented number as the baseline, not a contract. 429 responses carry `Retry-After` and `X-RateLimit-*`. ## Conventions - Prices are on the **0–100 cents scale** unless a field says otherwise (trader-analytics position/trade prices use the 0–1 scale; each field's description states its scale). - Errors: `{"detail": ""}` for handler errors; FastAPI's standard validation envelope for 422s. Errors surfaced from a venue adapter instead use `{"error", "provider", "operation", "message"}` — see `DataProviderError`. Unhandled failures always return the generic 500 body; internal details are logged, never returned. - Every request body is capped at 8 MiB service-wide (413). contact: name: Kairos url: https://app.kairos.trade/docs/api-reference termsOfService: https://kairos.trade/terms servers: - url: https://data.kairos.trade description: Production - url: https://staging-data.kairos.trade description: Staging security: - apiKeyClientId: [] apiKeyKey: [] apiKeySecret: [] paths: /txodds/fixtures: get: tags: - Sports summary: List sports fixtures with live status and win probabilities description: > Fixture board backed by the TxODDS score event store. Kick-off bounds are snapped to the minute — `from_ms` rounds down and `to_ms` rounds up, so the window may extend up to 59s past what was asked for. Per-row status is computed at cache time from feed phase plus wall clock, so a live-status flip can lag by up to one cache TTL. Concurrent misses on the same page share a single build. operationId: listTxoddsFixtures parameters: - name: competition_id in: query description: Restrict to one competition. schema: type: - integer - 'null' - name: sport in: query schema: type: - string - 'null' enum: - soccer - usfootball - name: from_ms in: query description: >- Kick-off lower bound, epoch milliseconds. Rounded down to the minute. schema: type: - integer - 'null' - name: to_ms in: query description: >- Kick-off upper bound, epoch milliseconds. Rounded up to the minute. When both bounds are given the span may not exceed 400 days. schema: type: - integer - 'null' - name: limit in: query schema: type: integer minimum: 1 maximum: 200 default: 50 - name: offset in: query description: Bounded so deep paging cannot mint unlimited cache keys. schema: type: integer minimum: 0 maximum: 5000 default: 0 responses: '200': description: One page of fixtures. content: application/json: schema: $ref: '#/components/schemas/TxoddsFixtureList' '401': $ref: '#/components/responses/DataUnauthorized' '403': $ref: '#/components/responses/DataForbidden' '422': description: > Parameter validation failed — unknown `sport`, out-of-range `limit`/`offset`, `from_ms` greater than `to_ms`, or a window wider than 400 days. The inverted/oversized-window cases return the plain `{"detail": "..."}` envelope, not the field-list envelope. content: application/json: schema: $ref: '#/components/schemas/DataError' example: detail: from_ms must not exceed to_ms '429': $ref: '#/components/responses/DataRateLimited' components: schemas: TxoddsFixtureList: type: object required: - items - limit - offset properties: items: type: array items: $ref: '#/components/schemas/TxoddsFixtureListItem' limit: type: integer description: Echo of the requested page size. offset: type: integer DataError: type: object description: Handler error envelope (FastAPI HTTPException). required: - detail properties: detail: type: string description: Human-readable error message. example: Invalid provider TxoddsFixtureListItem: type: object required: - fixtureId - competitionId - competition - home - away - kickoff properties: fixtureId: type: integer competitionId: type: integer competition: type: string home: $ref: '#/components/schemas/TxoddsTeamRef' away: $ref: '#/components/schemas/TxoddsTeamRef' kickoff: type: integer description: Kick-off, epoch milliseconds. winProb: oneOf: - $ref: '#/components/schemas/TxoddsWinProb' - type: 'null' status: type: string default: scheduled description: >- Derived from feed phase plus wall clock at cache time, so it can be up to one cache TTL stale. homeScore: type: integer default: 0 awayScore: type: integer default: 0 sport: type: string default: soccer TxoddsTeamRef: type: object required: - code - name properties: code: type: string name: type: string TxoddsWinProb: type: object required: - home - draw - away properties: home: type: number draw: type: number away: type: number responses: DataUnauthorized: description: > No valid credential presented — missing/invalid API-key headers, or an invalid/expired session token. content: application/json: schema: $ref: '#/components/schemas/DataError' example: detail: Not authenticated DataForbidden: description: > Authenticated but not permitted. Three distinct causes: the session user is not invited (`Invite required`), the API key lacks the operation's scope, or API-key access to the requested venue is switched off (`API access is disabled for `). Admin and API-key callers bypass the invite check; session and admin callers bypass scope and venue checks. content: application/json: schema: $ref: '#/components/schemas/DataError' example: detail: Invite required DataRateLimited: description: > Rate limit exceeded for this route's sliding window, keyed on the session `sub` when authenticated and on the trusted client IP otherwise. Honor `Retry-After`. A per-API-key data ceiling (set per credential) rejects with `{"detail": "API key data rate limit exceeded"}` instead of the `error` envelope below. headers: Retry-After: schema: type: integer X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer X-RateLimit-Reset: schema: type: integer content: application/json: schema: type: object properties: error: type: string example: 'Rate limit exceeded: 100 per 1 minute' securitySchemes: apiKeyClientId: type: apiKey in: header name: X-Client-Id description: >- Credential client id (`kairos_ck_...`). Must be sent together with X-Api-Key and X-Api-Secret. apiKeyKey: type: apiKey in: header name: X-Api-Key description: 64-char hex API key. apiKeySecret: type: apiKey in: header name: X-Api-Secret description: 64-char hex API secret. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.