> ## 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.

# Source-observed soccer and NFL fixture timing

> Fresh source clock evidence for one TxODDS fixture. No response caching or client countdown extrapolation. Missing, legacy, stale, interrupted, unsupported, or malformed evidence returns usableForLateGame=false with an explicit reason. Requires a verified fixture-to-market mapping before use by a trading strategy.



## OpenAPI

````yaml /openapi/data-api.yaml get /txodds/fixtures/{fixture_id}/timing
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": "<message>"}` 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/{fixture_id}/timing:
    get:
      tags:
        - Sports
      summary: Source-observed soccer and NFL fixture timing
      description: >-
        Fresh source clock evidence for one TxODDS fixture. No response caching
        or client countdown extrapolation. Missing, legacy, stale, interrupted,
        unsupported, or malformed evidence returns usableForLateGame=false with
        an explicit reason. Requires a verified fixture-to-market mapping before
        use by a trading strategy.
      operationId: getTxoddsFixtureTiming
      parameters:
        - name: fixture_id
          in: path
          required: true
          schema:
            type: integer
            minimum: 1
            exclusiveMaximum: 9223372036854776000
      responses:
        '200':
          description: Timing evidence, including explicit unavailability.
          headers:
            Cache-Control:
              schema:
                type: string
              description: no-store
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TxoddsFixtureTiming'
        '401':
          $ref: '#/components/responses/DataUnauthorized'
        '403':
          $ref: '#/components/responses/DataForbidden'
        '404':
          description: Fixture not found.
        '422':
          $ref: '#/components/responses/DataValidationError'
        '429':
          $ref: '#/components/responses/DataRateLimited'
        '500':
          description: Timing source unavailable; no eligible fallback is returned.
        '502':
          description: Invalid source observation.
components:
  schemas:
    TxoddsFixtureTiming:
      properties:
        fixtureId:
          title: Fixtureid
          type: integer
        competitionId:
          title: Competitionid
          type: integer
        sport:
          title: Sport
          type: string
        source:
          default: txodds
          title: Source
          type: string
        phase:
          anyOf:
            - type: string
            - type: 'null'
          default: null
          title: Phase
        status:
          default: unknown
          title: Status
          type: string
        observedAt:
          anyOf:
            - type: string
            - type: 'null'
          default: null
          title: Observedat
        evaluatedAt:
          title: Evaluatedat
          type: string
        stateAgeSeconds:
          anyOf:
            - type: number
            - type: 'null'
          default: null
          title: Stateageseconds
        staleAfterSeconds:
          default: 15
          title: Staleafterseconds
          type: integer
        stale:
          default: true
          title: Stale
          type: boolean
        clockSeconds:
          anyOf:
            - type: integer
            - type: 'null'
          default: null
          title: Clockseconds
        clockRunning:
          anyOf:
            - type: boolean
            - type: 'null'
          default: null
          title: Clockrunning
        clockDirection:
          default: unknown
          title: Clockdirection
          type: string
        periodRemainingSeconds:
          anyOf:
            - type: integer
            - type: 'null'
          default: null
          title: Periodremainingseconds
        regulationRemainingSeconds:
          anyOf:
            - type: integer
            - type: 'null'
          default: null
          title: Regulationremainingseconds
        gameRemainingSeconds:
          anyOf:
            - type: integer
            - type: 'null'
          default: null
          title: Gameremainingseconds
        elapsedMatchSeconds:
          anyOf:
            - type: integer
            - type: 'null'
          default: null
          title: Elapsedmatchseconds
        lateGameBasis:
          anyOf:
            - type: string
            - type: 'null'
          default: null
          title: Lategamebasis
        usableForLateGame:
          default: false
          title: Usableforlategame
          type: boolean
        unavailableReason:
          anyOf:
            - type: string
            - type: 'null'
          default: missing_score_observation
          title: Unavailablereason
      required:
        - fixtureId
        - competitionId
        - sport
        - evaluatedAt
      title: FixtureTiming
      type: object
      description: >-
        Source-observed fixture timing. Eligibility describes supported clock
        evidence, not whether a game is late or a market is safe to trade.
        Soccer exposes the nominal second-half clock, excluding any unknown
        added time; NFL exposes regulation clock time. No field predicts the
        final whistle or extrapolates between observations.
    DataError:
      type: object
      description: Handler error envelope (FastAPI HTTPException).
      required:
        - detail
      properties:
        detail:
          type: string
          description: Human-readable error message.
          example: Invalid provider
  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
        <provider>`). 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
    DataValidationError:
      description: Request failed FastAPI parameter validation.
      content:
        application/json:
          schema:
            type: object
            required:
              - detail
            properties:
              detail:
                type: array
                description: >-
                  One entry per failed field, with location, message, and error
                  type.
                items:
                  type: object
                  additionalProperties: true
    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.