fixture_idOne event. Connected sources.One consistent schema. Work with stable fixture IDs and normalized markets. Keep the source identity behind every observation.
The Developer Platform for Sports Odds
Sportsbooks, exchanges, and prediction markets. One API to connect your data, understand every price, and build your next idea.
REST APIWebSocketHistorical dataPythonTypeScriptOpenAPI
Bring your odds stack together with one platform for
prices and context.
Different sources. Different formats. The same integration work, again and again. Oddswire brings identity, prices, and history into a single developer workflow.
activeActive · stale · suspendedFreshness you can see. Know when a price was observed, when it changed, and when it is no longer eligible to use.
seen_tsOriginal time. Lasting context.Every change has a story. Explore retained price history with original timestamps and source provenance intact.
missing[]Clear reasons. Better decisions.Nothing silently missing. Understand unavailable coverage with explicit reasons. Build around the data you actually have.
Different markets.
One language for your code.
Spend your time building the product. Get structured observations with clear units, traceable sources, and explicit coverage.
BUILT FOR THE FULL PICTUREUnderstand the price.
Understand the price.
Keep the context.
A single observation carries its identity, native unit, state, and timestamp. Your application gets more than a number.
Stable canonical identifiersSource-native prices and unitsExplicit state and observation time
See the complete contract Price observationABRIDGED
{
"key": {
"source_id": 5,
"fixture_id": 100000,
"market_id": 1001,
"outcome_id": 10011,
"source_fixture_id": "example-fixture",
"side": "quote",
"depth": 0
},
"value": {
"state": "active",
"decimal_odds": "1.95000000",
"native_unit": "decimal_odds"
},
"seen_ts": "2026-11-09T12:00:00Z"
}Demonstration data. No live connection or API key required.Understand coverage
REST for the first request
A versioned contract, predictable pagination, and actionable errors.
Explore RESTA stream that stays in order
Snapshots, ordered deltas, and explicit resync when the context changes.
Explore WebSocketHistory with its context
Retained observations with original timestamps and coverage boundaries.
Explore historyA small first request.
A big head start.
Your language.
Your workflow.
Start with cURL, Python, or TypeScript. Use the same documented contract from your first request to your next integration.
Read the quick start Local SDK builds are available in the repository.request.sh
# Set your own key and entitled namespace privately.
# The local gateway must be running.
printf 'header = "X-API-Key: %s"\n' "$ODDEXA_API_KEY" |
curl --config - --silent --show-error --fail-with-body \
--get 'http://127.0.0.1:9113/v1/fixtures' \
--data-urlencode "namespace=$ODDEXA_NAMESPACE" \
--data-urlencode 'limit=1'Local gateway · Account-owned keyFull example
CONNECTED, WITH CONTEXTOne view across markets.
SPORTSBOOKSOdds, in their
PREDICTION MARKETSProbabilities,
A FOCUSED FIRST CHAPTERFootball first.
One view across markets.
Every source kept clear.
Connect sportsbook and prediction-market observations without losing what makes them different.
Explore coverageOdds, in their
native form.
Decimal prices with source, market, settlement, and state preserved.
BetRivers PAATG SE
Selected fixtures · Kambi source familyProbabilities,
with perspective.
Native probabilities remain distinct from decimal odds, with fee and settlement context.
Polymarket
Selected sports contractsFootball first.
Built to go further.
A pre-match pilot across six competitions. Explicit availability, down to each fixture.
1X2TotalsAsian handicap
Private pilot · Access reviewed per accountWhat will you build?
Odds comparison
Bring source-native prices into one consistent view.
Quantitative research
Understand price changes with retained historical evidence.
Prediction markets
Keep probabilities, sportsbook odds, and settlement context clear.
Your next big idea
Start with a documented contract. Build your own experience.
Explore today.
Build what comes next.
Start with the docs, understand the data, and take your first steps with the private beta.
Get to know the API.
Everything you need to understand the contract before writing your first integration.
- REST and WebSocket references
- Python and TypeScript guides
- Coverage and credit semantics
Build with Oddswire.
An account, your own API keys, and a workspace for your approved data access.
- Account-owned API keys
- Authenticated API playground
- Usage and source coverage
GOOD QUESTIONSA little more
A little more
clarity.
What can I build with Oddswire?
Use the API as a foundation for odds comparison, quantitative research, line-movement analysis, and prediction-market tools. Read the coverage and settlement context before comparing observations from different sources. Oddswire does not place bets or access sportsbook accounts.
Which sports and markets are in the pilot?
The initial pilot focuses on pre-match football across the Premier League, La Liga, Serie A, Bundesliga, Ligue 1, and Champions League. Selected 1X2, totals, and Asian handicap markets are in scope. Actual source and fixture availability is explicit in each response; the pilot is not a promise of complete league coverage.
Is the preview on this page live?
No. The interactive preview uses clearly labeled synthetic data to demonstrate the format and interface. It does not connect to a live feed or use a private API key. Account-specific coverage is available inside the authenticated workspace.
How do I get an API key?
Oddswire is preparing its private developer beta. The API reference and integration guides are open to explore today. Live data access will require an invitation and approved account access.
Do unsuccessful requests use credits?
Errors, conditional 304 responses, and account or control requests are free. A successfully delivered metered data response uses one credit, including an empty result. WebSocket messages do not consume REST credits. The docs explain the exact delivery and quota rules.