Skip to main content
Base URL: https://api.oddswire.io. Authenticate with an X-API-Key header. Paths already include /v1.

​
Start with three requests

  1. Check access. This free request returns your actual features, namespaces and source scope. A key does not grant data access.
  2. Find fixtures inside an entitled namespace. For a native-only source, use the native discovery routes below instead.
  3. Get odds for a discovered fixture or competition. Keep identifiers as returned, read missing[], and follow meta.next_cursor explicitly.
Run requests in the signed-in playground, or follow the cURL quick start. Nothing runs automatically in the playground.

​
Sports data

A single fixture is selected with the fixture filter; competition odds use competition. These are filters on the existing endpoints, not separate routes.

​
Dataset aliases and common records

Use the shorter kambi, pilot and sportsbooks aliases with the existing namespace parameter. Add view=standard to fixture/odds reads for consistent common fields and an unchanged original record. Existing calls keep their legacy shape. See Datasets and response views. New reads: Participants lists accessible team/player evidence; Fixture details retrieves one exact fixture. Native IDs remain source-scoped and do not imply verified player matching.

​
Native odds and player props

Native-only observations have a separate contract from canonical odds. They preserve provider fixture/market/selection IDs and units; they do not establish reviewed cross-book matching, player identity or settlement compatibility. Both native families use namespace oddswire_bookmakers and require their own explicit account features and source scope. Kambi source5 supports retained mode only; live mode applies only to separately approved sources14/15. Rediscover when a live capture is superseded. Retained snapshots preserve original times and must never be labelled current odds.

​
Access and quota

Use entitlements, coverage and usage before choosing a feed. These are free control reads. See requests, credits and errors for pagination, rate responses and uncertain delivery.

​
Advanced capabilities

Fair prices, reviewed mappings, history, WebSocket and alerts retain separate requirements. A documented schema does not mean a feature is available to your account. There is no eligible sharp reference configured for fair-price consensus. Scores, results/settlements, a complete player roster, languages and public paid account provisioning are not current sports-data endpoints. Request only operations documented in the OpenAPI contract.