Skip to main content

Choose canonical or source-native odds endpoints

Use the right fixture identity, capture and units for each endpoint family.

Oddswire separates reviewed canonical data from source-native observations. Choose the route family from the endpoint guide.

Canonical requests

Canonical /v1/fixtures and /v1/odds use canonical fixture identities within the selected namespace. Discover fixtures and source/region IDs there. Do not join different stores by coincident numeric IDs.

Native requests

Native routes use native_fixture, not a canonical fixture ID. Preserve original offer/outcome IDs and units. Kambi native odds additionally requires the original capture_id returned by discovery.

Kambi retained mode preserves the original snapshot time. Live mode has additional scope, freshness and source-control checks. Selecting live mode does not create a live entitlement.

Player props and comparisons

A source-labelled prop candidate is not automatically a reviewed player identity or compatible cross-source market. Read player, settlement and fee verification fields. A props filter selects available evidence; it does not establish full prop coverage.

Do not rename native IDs or convert units by assumption. Match the fixture, participant orientation, market, period, line and settlement before comparison. See Prices, coverage and fair values.

Did this answer your question?