A single gateway onto our sports odds feed. Bring your own API key, call any endpoint below
directly, and we handle connection management and consistent error handling so your integration
talks to one predictable API surface.
Base URL
__BASE_URL__
Replace with wherever this API is deployed. Every path below is relative to it.
Authentication
Pass your API key as apiKey on every request.
Response format
Every endpoint returns a plain JSON body with a standard HTTP status code — nothing reshaped, nothing renamed.
Latency
Responses typically return in well under a second, with only a few ms of overhead added by us.
Quick reference
13 endpoints
Every route this API exposes, at a glance. Click a path to jump to its full parameter list and example response.
[{"marketId":101,"marketName":"Full Time Result","marketType":"1x2","outcomes":[{"outcomeId":101,"outcomeName":"1"},{"outcomeId":102,"outcomeName":"X"}]}]
Results
2 endpoints
What happened — settled outcomes and live/final scores.
GET/api/settlementsBillable
Settled result (win/lose/push) for every outcome on a fixture.
Errors use standard HTTP status codes with a JSON body describing what went wrong. Two error shapes are specific to this API — everything else follows the endpoint's own error format.
Status
Meaning
4xx / 5xx
The request was rejected or failed — bad parameters, exhausted quota, etc. The response body describes what went wrong.
404
No such endpoint. { "error": "Not Found", "message": "…" }
502
We couldn't process the request right now (temporary connectivity issue). { "error": "Bad Gateway", "message": "…" }
Every call counts against your plan's quota — we don't add any separate limits on top.
Billable
1 request = 1 call, counted regardless of response size or status. Most endpoints fall in this tier.
Free
/api/historical-odds never counts against your quota, however often it's called.
Each endpoint enforces roughly a 1-second cooldown between calls with identical parameters. Calling
the same endpoint faster than that may get rate-limited — we don't currently smooth that out with
local throttling or caching.