This section details the most important information when working with the unified odds API.

Self-service documentation

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).

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>

Administrative

The following is an administrative message that can be used to find out what the callers bookmaker id is (which is needed to find the name of the AMQP vhost to connect to), and when the callers access token will expire.

HTTP

Endpoint

Description

GET

users/whoami.xml

Lists the callers bookmaker id, AMQP access point and when the provided access token will expire.

<bookmaker_details response_code="OK" expire_at="2016-07-08T11:58:53Z" bookmaker_id="15879" virtual_host="/unifiedfeed/15879"/>

Result codes for users/whoami.xml:

Token

HTTP Response Code

Description

Valid token provided

200

OK

No token provided

400

Bad Request

Unknown Token

404

Not found

Expired token

403

Forbidden: “Error: Token is not valid, perhaps it has expired?”

UF Package Missing

403

Forbidden: “Error: Bookmaker <id> does not have access to unified feed”


Back to top