> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oddswire.io/llms.txt
> Use this file to discover all available pages before exploring further.

# API overview

> Check access, discover fixtures and request odds through the current REST API.

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

## Start with three requests

1. [Check access](https://docs.oddswire.io/reference/getEntitlements.md). This free request returns your actual features, namespaces and source scope. A key does not grant data access.
2. [Find fixtures](https://docs.oddswire.io/reference/listFixtures.md) inside an entitled namespace. For a native-only source, use the native discovery routes below instead.
3. [Get odds](https://docs.oddswire.io/reference/listOdds.md) 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](https://oddswire.io/app/playground), or follow the [cURL quick start](https://docs.oddswire.io/quickstart-curl.md). Nothing runs automatically in the playground.

## Sports data

| GET endpoint | Use it for |
| - | - |
| [`/v1/sports`](https://docs.oddswire.io/reference/listSports) | Discover sports in your scope |
| [`/v1/bookmakers`](https://docs.oddswire.io/reference/listSources) | Source and region identities, including feed-family relationships |
| [`/v1/competitions`](https://docs.oddswire.io/reference/listCompetitions) | Competitions, optionally filtered by sport |
| [`/v1/markets`](https://docs.oddswire.io/reference/listMarkets) | Market families and periods |
| [`/v1/fixtures`](https://docs.oddswire.io/reference/listFixtures) | Fixtures filtered by source, sport, competition or time |
| [`/v1/odds`](https://docs.oddswire.io/reference/listOdds) | Scoped odds pages with explicit state, units and missing coverage |

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](https://docs.oddswire.io/datasets.md).

New reads: [Participants](https://docs.oddswire.io/reference/listParticipants.md) lists accessible team/player evidence; [Fixture details](https://docs.oddswire.io/reference/getFixture.md) 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.

| GET endpoint | Use it for |
| - | - |
| [`/v1/native/fixtures`](https://docs.oddswire.io/reference/listNativeFixtures) | Discover reviewed source11/12/13 fixtures using an explicit `source_id` |
| [`/v1/native/odds`](https://docs.oddswire.io/reference/listNativeOdds) | Request a returned `native_fixture`; `props_only=true` selects source-labelled prop candidates |
| [`/v1/native/kambi/fixtures`](https://docs.oddswire.io/reference/listKambiNativeFixtures) | Discover source5/14/15 snapshots in `retained` or separately approved `live` mode |
| [`/v1/native/kambi/odds`](https://docs.oddswire.io/reference/listKambiNativeOdds) | Request the exact returned `native_fixture` and `capture_id`; optionally filter with `props_only=true` |

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](https://docs.oddswire.io/reference/getEntitlements.md), [coverage](https://docs.oddswire.io/reference/getAccountCoverage.md) and [usage](https://docs.oddswire.io/reference/getUsage.md) before choosing a feed. These are free control reads. See [requests, credits and errors](https://docs.oddswire.io/errors.md) for pagination, rate responses and uncertain delivery.

## Advanced capabilities

[Fair prices](https://docs.oddswire.io/reference/getFair.md), [reviewed mappings](https://docs.oddswire.io/reference/listMappings.md), [history](https://docs.oddswire.io/history.md), [WebSocket](https://docs.oddswire.io/websocket.md) and [alerts](https://docs.oddswire.io/alerts.md) 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](https://docs.oddswire.io/openapi.json).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.