Overview
Self-service Documentation
API Authentication
x-access-token: <access token> XSD Schemas
Token Result Codes
Last updated
Was this helpful?
This section details the most important information when working with the unified odds API.
All endpoints are available for testing purposes at http://iodocs.betradar.com. From there you can see each of the endpoints, execute the requests, and see sample responses as long as you have an access-token (see below - authentication)
To access the API, you must visit Betradar.com and generate an application key associated with your Betradar.com user details. This API key has to be sent as an HTTP header on every request towards the service on the following format:
x-access-token: <access token> If you already have a Unified Odds Feed access token, please use the same to authorize your API access
Info
Our endpoints are backed by Content Delivery Network (CDN) solution to ensure low latency from geographically distributed locations. The DNS names (mq.betradar.com, api.betradar.com, global.mq.betradar.com and global.api.betradar.com) will point to a set of IP addresses, and those IP addresses can change from time to time without prior notice.
If you currently whitelist our IP for outgoing traffic, we can not supply you with a fixed set of IPs for this, as they can change from time to time and without prior notice.
Token
HTTP Response Code
Description
Valid token provided
No token provided
No token provided
Unknown Token
Expired token
UF Package Missing
Last updated
Was this helpful?
Was this helpful?
200OK400Bad Request401Inauthorized404Not found403Forbidden: “Error: Token is not valid,
perhaps it has expired?”403Forbidden: “Error: Bookmaker <id>
does not have access to unified feed”