Your Sports Data Feed
Provider
Technical Documentation
Below you will find a general explanation of all available messages and connections in order to
successfully connect your system to our feed. The feed consists of XML messages pushed via
AMQP with real-time information and API’s to provide metadata.
RMQ Messages
Messages regarding Fixture Changes, Odds Changes and Bet Settlements will be provided over
RMQ messages.
In order to connect to the RMQ you will be provided with login credentials (username and
password) as well as Queue name, port and vhost to which you will be connecting to. Your IP
addresses must be whitelisted in order for the connection to work.
API Metadata
Additional data such as Fixtures will be provided over API calls which are independent of the
RMQ. Every API call has it’s own definition, type of request and required fields.
RMQ Messages
Messages regarding New Events, Odds Changes and Bet Settlements will be provided over RMQ
messages.
Alive
Once you are successfully connected to the queue you will start to receive Alive Messages every
minute (Depending on the product). This is indicating that the service is operating normally and
you are able to receive messages from us.
Your Sports Data Feed
Provider
If you stop receiving alive messages at the expected intervals, it is indicating that something
might be wrong with the connection between our service and yours. It is important to look at the
timestamp inside the alive messages, and the time interval in which you receive them. If the
timestamp inside the messages is consistent at the indicated time per product but you receive the
messages at a slower pace, this might indicate a bad network connection between your servers
and our service, or slow processing on your side. If the timestamp inside the alive messages is
approximately more than the indicated interval, this indicates something is wrong on our side
and you should contact us directly.
XML Attributes
NAME
DESCRIPTION
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
XML Example
<?xml version='1.0' encoding='utf-8'?>
<alive product_id="1" timestamp="1695889437000"/> Product
Interval
NAME
Seconds
Prematch
60 Seconds
Live
10 Seconds
Fixture Change
A fixture_change message is sent when a new update in a fixture is published. This message
includes the following attributes:
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event
product_id
The ID of the product
change_id
The ID of the type of change
Your Sports Data Feed
Provider
timestamp
The date & time of when the message was created (UTC)
Fixture Change IDs
ID
DESCRIPTION
1
This indicates that a new Fixture was published
2
This indicates that there was a change in Date & Time
Each event_id is sent in a seperate message therefore each fixture_change message can only
containt 1 event ID.
When you receive the message above you should call the following API to get the latest Fixture
Data:
XML Example
<?xml version='1.0' encoding='utf-8'?>
<fixture_change event_id="match:131754" change_id="1" product_id="1"
timestamp="1695889437000"/>
Odds Change
An odds_change message is sent when the odds updates for a fixture are published. This
message includes the following attributes:
XML Attributes
NAME
DESCRIPTION
product_id
The ID of the product
event_id
The ID of the event (Match or Outright)
timestamp
The date & time of when the message was created (UTC)
event status
The status of the event
score_1
The current score of the home/type1 team (Only for Live)
score_2
The current score of the away/type2 team (Only for Live)
Your Sports Data Feed
Provider
match_time
The current time of the match. Format is mm:ss (Only for Live)
stoppage_time
The current stoppage time of the match. Format is mm:ss (Only for Live)
market id
The ID of the market
market status
The status of the market
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the market
such as Spread. (Not always available)
outcome id
The ID of the outcome
outcome status
The status of the outcome
odds
The latest odds for the outcome
Status IDs
ID
0
1
Each event_id is sent in a seperate message therefore each odds_change message can only
containt 1 event ID.
To resend the latest odds in the queue you can use the following POST API
Your Sports Data Feed
Provider
XML Examples
Match Odds
<?xml version='1.0' encoding='utf-8'?>
<odds_change product_id="2" event_id="match:131718" timestamp="1695889437000">
<sport_event_status status="1" score_1="0" score_2="0">
<clock match_time="90:00" stoppage_time="02:25"/>
</sport_event_status>
<odds>
<market id="3" status="1" specifiers="spread=18.5">
<outcome id="6" status="1" odds="2"/>
<outcome id="7" status="1" odds="1.7"/>
</market>
</odds>
</odds_change>
Match Deactivation
<?xml version='1.0' encoding='utf-8'?>
<odds_change product_id="1" event_id="match:131718"
timestamp="1695889437000"> <sport_event_status
status="0"/>
</odds_change>
Market Deactivation
<?xml version='1.0' encoding='utf-8'?>
<odds_change product_id="2" event_id="match:131718" timestamp="1695889437000">
<sport_event_status status="1"
<odds>
<market id="3" status="0" specifiers="spread=18.5"/>
</odds>
</odds_change>
Outright Odds
<?xml version='1.0' encoding='utf-8'?>
<odds_change product_id="1" event_id="outright:131728"
timestamp="1695889437000"> <sport_event_status
status="1"/>
<odds>
<market id="101" status="1">
<outcome id="40000000" status="1" odds="1.8"/>
<outcome id="40000001" status="1" odds="3"/>
<outcome id="40000004" status="0"/>
<outcome id="40000002" status="1" odds="40"/>
Your Sports Data Feed
Provider
</market>
</odds>
</odds_change>
Outright Deactivation
<?xml version='1.0' encoding='utf-8'?>
<odds_change product_id="1" event_id="outright:131728"
timestamp="1695889437000"> <sport_event_status
status="0"/>
</odds_change>
Player Odds Change
A player_odds_change message is sent when the player odds updates for a fixture are published.
This message includes the following attributes:
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event
status
The status of the event
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
competitor id
The ID of the competitor
player id
The ID of the player
player status
The status of the player
market id
The ID of the market
market status
The status of the market
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the market
such as Spread. (Not always available)
outcome id
The ID of the outcome
Your Sports Data Feed
Provider
outcome
status
The status of the outcome
odds
The latest odds for the outcome
Status IDs
ID
0
1
Each event_id is sent in a seperate message therefore each odds_change message can only
containt 1 event ID.
To resend the latest odds in the queue you can use the following POST API:
XML Examples
Player Odds
<?xml version='1.0' encoding='utf-8'?>
<player_odds_change event_id="match:131728" product_id="4"
timestamp="1695889437000">
<sport_event_status status="1"/>
<competitor id="7">
<player id="1984029" status="1">
<odds>
<market id="2000" status="1" specifiers="spread=45.5">
<outcome id="6" status="1" odds="1.8"/>
<outcome id="7" status="1"
odds="1.9"/>
</market>
<market id="2001" status="1"
specifiers="spread=37.5">
<outcome id="6" status="1" odds="1.8"/>
<outcome id="7" status="1"
odds="1.8"/>
</market>
</odds>
</player>
<player id="1984030" status="1">
<odds>
<market id="2000" status="1"
specifiers="spread=45.5">
<outcome id="6" status="1" odds="1.8"/>
<outcome id="7" status="1"
odds="1.9"/>
Your Sports Data Feed
Provider
</market>
</odds>
</player>
</competitor>
<competitor id="25">
<player id="1984032" status="1">
<odds>
<market id="2000" status="1" specifiers="spread=45.5">
<outcome id="6" status="1" odds="1.8"/>
<outcome id="7" status="1"
odds="1.9"/>
</market>
</odds>
</player>
<player id="1984033" status="1">
<odds>
<market id="2000" status="1"
specifiers="spread=45.5">
<outcome id="6" status="1" odds="1.8"/>
<outcome id="7" status="1"
odds="1.9"/>
</market>
</odds>
</player>
</competitor>
</player_odds_change>
Match Deactivation
<?xml version='1.0' encoding='utf-8'?>
<player_odds_change product_id="4" event_id="match:131728"
timestamp="1695889437000"> <sport_event_status
status="0"/>
</player_odds_change>
Player Deactivation
<?xml version='1.0' encoding='utf-8'?>
<player_odds_change event_id="match:131728" product="4"
timestamp="1659433219446">
<sport_event_status status="1"/>
<competitor id="7">
<player id="1984031" status="0"/>
</competitor>
<competitor id="25">
<player id="1984034" status="0"/>
</competitor>
</player_odds_change>
Your Sports Data Feed
Provider
Market Deactivation
<?xml version='1.0' encoding='utf-8'?>
<player_odds_change event_id="match:131728" product="4"
timestamp="1695889437000">
<sport_event_status status="1"/>
<competitor id="7">
<player id="1984030" status="1">
<odds>
<market id="2001" status="0"
specifiers="spread=37.5"/>
</odds>
</player>
<player id="1984031" status="0"/>
</competitor>
<competitor id="25">
<player id="1984033" status="1">
<odds>
<market id="2001" status="0"
specifiers="spread=37.5"/>
</odds>
</player>
</competitor>
</player_odds_change>
Bet Stop
An bet_stop message is sent when the odds need to be instantly suspended (continue to display
odds, but don’t accept bets). This message includes the following attributes:
XML Attributes
NAME
DESCRIPTION
product_id
The ID of the product
event_id
The ID of the event (Match or Outright)
timestamp
The date & time of when the message was created (UTC)
XML Examples
Bet Stop
<?xml version='1.0' encoding='utf-8'?>
Your Sports Data Feed
Provider
<bet_stop product_id="2" event_id="match:131718" timestamp="1695889437000"/>
Bet Settlement
A bet_settlement message is sent when a new result in a fixture is published. This message
includes the following attributes:
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event (Match or Outright)
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
market id
The ID of the market
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the
market such as Spread. (Not always available)
outcome id
The ID of the outcome
result
The result of the outcome
void_factor
The type of void of the outcome (Not always available)
Result IDs
ID
Void
DESCRIPTION
0
This indicates that the outcome is Lost
Your Sports Data Feed
Provider
1
This indicates that the outcome is Won
0
1.0
This indicates that the outcome should be Voided
1
0.5
This indicates that the outcome should be half Won and half Voided
0
0.5
This indicates that the outcome should be half Lost and half Voided
To resend the settlements in the queue you can use the following POST API
XML Examples
Match Settlements
<?xml version='1.0' encoding='utf-8'?>
<bet_settlement product_id="1" event_id="match:131718"
timestamp="1695889437000">
<settlements>
<market id="3" specifiers="spread=18.5">
<outcome id="6" result="1"/>
<outcome id="7" result="0"/>
</market>
</settlements>
</bet_settlement>
Outright Settlements
<?xml version='1.0' encoding='utf-8'?>
<bet_settlement product_id="1" event_id="outright:131728"
timestamp="1695889437000">
<settlements>
<market id="101">
<outcome id="40000000" result="0"/>
<outcome id="40000001" result="1"/>
<outcome id="40000004" result="0" void_factor="1.0"/>
<outcome id="40000002" result="0"/>
</market>
</settlements>
</bet_settlement>
Rollback Bet Settlement
A rollback_bet_settlement message is sent when a previous bet settlement needs to be rolled
back/undone and following it you will receive a new bet_settlement message with the new
settlements. This message includes the following attributes:
Your Sports Data Feed
Provider
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
market id
The ID of the market
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the market
such as Spread. (Not always available)
XML Examples
Rollback Bet Settlements
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rollback_bet_settlement product_id="1" event_id="match:131718"
timestamp="1695889437000">
<settlements>
<market id="1" specifiers="spread=18.5"/>
<market id="1" specifiers="spread=19.5"/>
<market id="2" specifiers="spread=19.5"/>
<market id="3"/>
</settlements>
</rollback_bet_settlement>
Player Bet Settlement
A player_bet_settlement message is sent when the player settlements for a fixture are published.
This message includes the following attributes:
Your Sports Data Feed
Provider
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
market id
The ID of the market
player id
The ID of the player
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the
market such as Spread. (Not always available)
outcome id
The ID of the outcome
result
The result of the outcome
void_factor
The type of void of the outcome (Not always available)
Result IDs
ID
Void
DESCRIPTION
0
This indicates that the outcome is Lost
1
This indicates that the outcome is Won
0
1.0
This indicates that the outcome should be Voided
To resend the player settlements in the queue you can use the following POST API.
Your Sports Data Feed
Provider
XML Examples
Player Bet Settlements
<?xml version='1.0' encoding='utf-8'?>
<player_bet_settlement event_id="match:131718" product_id="4"
timestamp="1695889437000">
<settlements>
<market id="2000">
<player player_id="159665" specifiers="spread=20.5" outcome_id="6"
result="1"/>
<player player_id="159665" specifiers="spread=20.5" outcome_id="7"
result="0"/>
<player player_id="159665" specifiers="spread=19.5" outcome_id="6"
result="1"/>
<player player_id="159665" specifiers="spread=19.5" outcome_id="7"
result="0"/>
<player player_id="159666" specifiers="spread=20.5"
outcome_id="6" result="0" void_factor="1.0"/>
<player player_id="159666" specifiers="spread=20.5"
outcome_id="7" result="0" void_factor="1.0"/>
<market/>
<market id="2001">
<player player_id="159665" specifiers="spread=20.5" outcome_id="6"
result="1"/>
<player player_id="159665" specifiers="spread=20.5" outcome_id="7"
result="0"/>
<player player_id="159665" specifiers="spread=19.5" outcome_id="6"
result="1"/>
<player player_id="159665" specifiers="spread=19.5" outcome_id="7"
result="0"/>
<player player_id="159666" specifiers="spread=20.5"
outcome_id="6" result="0" void_factor="1.0"/>
<player player_id="159666" specifiers="spread=20.5"
outcome_id="7" result="0" void_factor="1.0"/>
<market/>
<settlements>
<player_bet_settlement/>
Your Sports Data Feed
Provider
Rollback Player Bet Settlement
A rollback_player_bet_settlement message is sent when a previous player bet settlement needs to
be rolled back/undone and following it you will receive a new player_bet_settlement message with
the new settlements. This message includes the following attributes:
XML Attributes
NAME
DESCRIPTION
event_id
The ID of the event
product_id
The ID of the product
timestamp
The date & time of when the message was created (UTC)
market id
The ID of the market
player id
The ID of the player
market
specifiers
A | separated list of key=value-pairs. These are further specifiers for the market
such as Spread. (Not always available)
XML Examples
Rollback Player Bet Settlements
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rollback_player_bet_settlement product_id="4" event_id="match:347596"
timestamp="1701104537152"> <settlements>
<market id="2000">
<player player_id="25008438" specifiers="spread=11.5"/>
<player player_id="25008438" specifiers="spread=10.5"/>
<player player_id="25008453" specifiers="spread=13.5"/>
</market>
<market id="2107">
<player player_id="25008438" specifiers="spread=11.5"/>
<player player_id="25008438" specifiers="spread=10.5"/>
<player player_id="25008453" specifiers="spread=13.5"/>
Your Sports Data Feed
Provider
</market>
<market id="2104">
<player player_id="25008438" specifiers="spread=11.5"/>
<player player_id="25008438" specifiers="spread=10.5"/>
<player player_id="25008453" specifiers="spread=13.5"/>
</market>
</settlements>
</rollback_player_bet_settlement>
GET - Fixture
When you receive a new event inside fixture_change message you should use that data to request
the Fixture using the following GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/v1/fixtures/{eventid}
GET
Event ID
/api/v1/fixtures/{131718}
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created (UTC)
event_id
The ID of the event (Match or Outright)
event_name
The name of the event (only for Outright)
expiry_date
The next expiration date of the event (Not always available)
scheduled_date
The date of when the event will take place
sport id
The ID of the sport
sport name
The name of the sport
category id
The ID of the category
category name
The name of the category
tournament id
The ID of the tournament
tournament name
The name of the tournament
Your Sports Data Feed
Provider
outcome id
The ID of the outcome (only for outright)
outcome name
The name of the outcome (only for outright)
competitor id
The ID of the competitor (only for match)
competitor name
The name of the competitor (only for match)
competitor type
The position of the competitor (this should be used to determine home and
away)
reference id
The mapping id for a particular FeedProvider/Bookmaker
reference name
The name of the FeedProvider/Bookmaker mapping id
reference type
The entity of the FeedProvider/Bookmaker mapping id
Response Examples
One Competitor Match Fixture
<?xml version="1.0" encoding="UTF-8"?>
<fixtures_fixture timestamp="1695889437000">
<fixture event_id="match:131719" expiry_date="2023-1003T13:00:00+00:00"
scheduled_date="2023-10-05T13:00:00+00:00">
<sport id="10040" name="Formula 1"/>
<category id="20" name="Brazil"/>
<tournament id="19" name="Classified/Not Classified"/>
<competitors>
<competitor id="40000000" name="Verstappen, Max"/>
</competitors>
</fixture>
</fixtures_fixture>
Two Competitor Match Fixture
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fixtures_fixture timestamp="1701966942002">
<fixture scheduled_date="2023-12-08T02:00:00+00:00"
event_id="match:353514">
<sport id="1002" name="Basketball"/>
<category id="79" name="USA"/>
<tournament id="167" name="NBA"/>
<competitors>
<competitor id="1394" name="Los Angeles Lakers" type="1">
<reference_ids>
<reference id="3427" name="betradar"/>
</reference_ids>
</competitor>
<competitor id="1527" name="New Orleans Pelicans" type="2">
Your Sports Data Feed
Provider
<reference_ids>
<reference id="5539" name="betradar"/>
</reference_ids>
</competitor>
</competitors>
<reference_ids>
<reference id="45979419" name="betradar" type="Match"/>
<reference id="132" name="betradar" type="Tournament"/>
<reference id="2" name="betradar" type="Sport"/>
<reference id="15" name="betradar" type="Category"/>
</reference_ids>
</fixture> </fixtures_fixture>
Outright Fixture
<?xml version="1.0" encoding="UTF-8"?>
<fixtures_fixture timestamp="1695889437000">
<fixture event_id="outright:131728" event_name="Group 1 Winner"
expiry_date="2023-10-03T13:00:00+00:00" scheduled_date="2023-
1005T13:00:00+00:00">
<sport id="10040" name="Formula 1"/>
<category id="20" name="Brazil"/>
<tournament id="17" name="Group 1 Winner"/>
<outcomes>
<outcome id="40000000" name="Verstappen, Max"/>
Charles"/>
<outcome id="40000001" name="Leclerc,
<outcome id="40000002" name="Perez, Sergio"/>
Carlos"/>
<outcome id="40000004" name="Sainz Jr,
</outcomes>
</fixture>
</fixtures_fixture>
GET - Competitor Information
This API is used to retreive data related to the competitor. When inserting the competitor id you
will get related information such as the competitor name and the player list (if any). To request
this API you should use the following GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/v1/competitors/{competitorid}
GET
Competitor
ID
/api/v1/competitors/{1394}
Your Sports Data Feed
Provider
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created
competitor id
The ID of the competitor
competitor name
The name of the competitor
player id
The ID of the player
player name
The name of the player
reference id
The mapping id for a particular FeedProvider/Bookmaker
reference name
The name of the FeedProvider/Bookmaker mapping id
Response Examples
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<competitor id="1394" name="Los Angeles Lakers" timestamp="1701947572956">
<players>
<player id="25004285" name="Dennis Schroder"/>
<player id="25005076" name="Rui Hachimura"/>
<player id="25006572" name="Shaquille Harrison"/>
<player id="25006573" name="D'Angelo Russell"/>
<player id="25006574" name="Jalen Hood Schifino"/>
<player id="25006575" name="Jarred Vanderbilt"/>
<player id="25006576" name="Anthony Davis"/>
<player id="25006577" name="Lonnie Walker"/>
<player id="25006578" name="Malik Beasley"/>
<player id="25006579" name="LeBron James"/>
<player id="25006580" name="Troy Brown"/>
<player id="25006581" name="Tristan Thompson"/>
<player id="25006582" name="Max Christie"/>
<player id="25006583" name="Mo Bamba"/>
<player id="25006584" name="Scotty Pippen"/>
<player id="25006585" name="Austin Reaves"/>
<player id="25006587" name="Cole Swider"/>
<player id="25006588" name="Maxwell Lewis"/>
<player id="25006590" name="Wenyen Gabriel"/>
</players>
<reference_ids>
<reference id="3427" name="betradar"/>
</reference_ids>
</competitor>
Your Sports Data Feed
Provider
GET - Player Information
This API is used to retreive data related to the player. When inserting the player id you will get
related information such as the player name, reference ids and competitors. To request this API
you should use the following GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/v1/players/{playerid}
GET
Player ID
/api/v1/players/{25006579}
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created
player id
The ID of the player
player name
The name of the player
player fullname
The full name of the player
competitor id
The ID of the competitor
competitor name
The name of the competitor
reference id
The mapping id for a particular FeedProvider/Bookmaker
reference name
The name of the FeedProvider/Bookmaker mapping id
Your Sports Data Feed
Provider
Response Examples
<?xml version='1.0' encoding='utf-8'?>
<player id="25006579" name="LeBron J." fullname="LeBron James"
timestamp="1687877080730">
<competitors>
<competitor id="1394" name="Los Angeles Lakers"/>
<competitor id="2111" name="USA"/>
</competitors>
<reference_ids>
<reference id="608028" name="betradar"/>
</reference_ids>
</player>
GET - Market List
This API is used to retreive data related to the list of markets. When inserting the sport id you
will get related markets and outcomes for the sport requested (If you do not insert any sport id
you will the list of all markets for all sports). To request this API you should use the following
GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/v1/marketData/
GET
Sport ID (optional)
/api/v1/marketData?sport_id=1002
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created
market id
The ID of the market
market name
The name of the market
market specifier
The specifier of that market (Not always available)
outcome id
The ID of the outcome
outcome name
The name of the outcome
Response Examples
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<market_descriptions timestamp="1701966942002">
<market id="2000" name="Points" specifier="spread">
Your Sports Data Feed
Provider
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2001" name="Assists" specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2002" name="Rebounds" specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2003" name="3-Pointers" specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2100" name="Total Points + Total Assists" specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2101" name="Total Points + Total Rebounds" specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2102" name="Total Assists + Total Rebounds"
specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2103" name="Total Points + Total Assists + Total Rebounds"
specifier="spread">
<outcomes>
<outcome id="6" name="Over"/>
<outcome id="7" name="Under"/>
</outcomes>
</market>
<market id="2104" name="2-way + Total Points" specifier="spread">
<outcomes>
<outcome id="1019" name="1 + Over"/>
<outcome id="1020" name="1 + Under"/>
<outcome id="1021" name="2 + Over"/>
Your Sports Data Feed
Provider
<outcome id="1022" name="2 + Under"/>
</outcomes>
</market>
<market id="2105" name="2-way + Total Assists" specifier="spread">
<outcomes>
<outcome id="1019" name="1 + Over"/>
<outcome id="1020" name="1 + Under"/>
<outcome id="1021" name="2 + Over"/>
<outcome id="1022" name="2 + Under"/>
</outcomes>
</market>
<market id="2106" name="2-way + Total Rebounds" specifier="spread">
<outcomes>
<outcome id="1019" name="1 + Over"/>
<outcome id="1020" name="1 + Under"/>
<outcome id="1021" name="2 + Over"/>
<outcome id="1022" name="2 + Under"/>
</outcomes>
</market>
<market id="2107" name="Odd/Even + Total Points" specifier="spread">
<outcomes>
<outcome id="9000" name="Odd + Over"/>
<outcome id="9001" name="Odd + Under"/>
<outcome id="9002" name="Even + Over"/>
<outcome id="9003" name="Even + Under"/>
</outcomes>
</market>
<market id="2108" name="Odd/Even + Total Assists" specifier="spread">
<outcomes>
<outcome id="9000" name="Odd + Over"/>
<outcome id="9001" name="Odd + Under"/>
<outcome id="9002" name="Even + Over"/>
<outcome id="9003" name="Even + Under"/>
</outcomes>
</market>
<market id="2109" name="Odd/Even + Total Rebounds" specifier="spread">
<outcomes>
<outcome id="9000" name="Odd + Over"/>
<outcome id="9001" name="Odd + Under"/>
<outcome id="9002" name="Even + Over"/>
<outcome id="9003" name="Even + Under"/>
</outcomes>
</market>
</market_descriptions>
Your Sports Data Feed
Provider
GET - Timeline
When you receive an event inside bet_settlement message you should use that data to request the
Timeline of the match using the following GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/live/v1/timeline/{eventid}
GET
Event ID
/api/v1/timeline/{3535142}
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created (UTC)
event_id
The ID of the event
sport id
The ID of the sport
sport name
The name of the sport
category id
The ID of the category
category name
The name of the category
tournament id
The ID of the tournament
tournament
name
The name of the tournament
competitor id
The ID of the competitor
competitor name
The name of the competitor
competitor type
The position of the competitor (this should be used to determine home and
away)
reference id
The mapping id for a particular FeedProvider/Bookmaker
Your Sports Data Feed
Provider
reference name
The name of the FeedProvider/Bookmaker mapping id
reference type
The entity of the FeedProvider/Bookmaker mapping id
1_score
The score of the home/type1 team
2_score
The score of the away/type2 team
match_status_id
The id for the status of the match
score_status_id
The id for the type of Score
Response Examples
Timeline
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<match_timeline timestamp="1701966942002">
<fixture event_id="match:3535142">
<sport id="1001" name="Soccer"/>
<category id="49" name="Spain"/>
<tournament id="184" name="La Liga"/>
<competitors>
<competitor id="2345" name="Girona" type="1">
<reference_ids>
<reference id="3427" name="betradar"/>
</reference_ids>
</competitor>
<competitor id="2243" name="Villarreal" type="2">
<reference_ids>
<reference id="5539" name="betradar"/>
</reference_ids>
</competitor>
</competitors>
<reference_ids>
<reference id="45979419" name="betradar" type="Match"/>
<reference id="132" name="betradar" type="Tournament"/>
<reference id="2" name="betradar" type="Sport"/>
<reference id="15" name="betradar" type="Category"/>
</reference_ids>
</fixture>
<sport_event_status match_status_id="100">
<scores>
<score score_status_id="200" score_1="0" score_2="1"/>
<score score_status_id="6" score_1="0" score_2="0"/>
<score score_status_id="7" score_1="0" score_2="1"/>
<score score_status_id="31" score_1="0" score_2="0"/>
</scores>
</sport_event_status>
</match_timeline>
Your Sports Data Feed
Provider
GET - Match/Score Status
This API is used to retreive the data related to the list of the Match Status and Score StatusIDs
found in the API. When requesting you will get the related ids and names for the related status
including to which sports they are connected to. To request this API you should use the following
GET API data:
Endpoint
Method
Input Data
Sample Request Body
/api/live/v1/statusMatchScore
GET
N/A
/api/live/v1/statusMatchScore
Response Attributes
NAME
DESCRIPTION
timestamp
The date & time of when the message was created
status id
The ID of the status
status name
The name/type of the status
sport id
The ID of the Sport in which the status is included
sport name
The Name of the Sport in which the status is included
Response Examples
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<status_match_score timestamp="1701966942002">
<status id="100" name="Ended">
<sports>
<sport id="1001" name="Soccer"/>
<sport id="1002" name="Basketball"/>
<sport id="1005" name="Tennis"/>
</sports>
</status>
<status id="50" name="Penalties">
<sports>
<sport id="1001" name="Soccer"/>
</sports>
</status>
<status id="6" name="1st Half">
<sports>
<sport id="1001" name="Soccer"/>
<sport id="1002" name="Basketball"/>
Your Sports Data Feed
Provider
</sports>
</status>
</match_score_status>
POST - Odds
If you would like to resend the odd changes for any specific event_id/s you can use to following
POST API data which will send any odds_change or player_odds_change messages in the queue.
Endpoint
Method
Input Body
Sample Request Body
/api/v1/oddsChange
POST
Event ID
{
"eventIds": [ 134663, 131719]
}
The response Body should be as follows:
<?xml version='1.0' encoding='utf-8'?>
<response timestamp="1673531781" response_code="ACCEPTED"/>
POST - Bet Settlement
If you would like to resend the bet settlements for any specific event_id/s you can use to
following POST API data which will send bet_settlement or player_bet_settlement messages in
the queue.
Endpoint
Method
Input Body
Sample Request Body
/api/v1/betsettlement
POST
Event ID
{
"eventIds": [ 134663, 131719]
}
The response Body should be as follows:
<?xml version='1.0' encoding='utf-8'?>
<response timestamp="1673531781" response_code="ACCEPTED"/>
Your Sports Data Feed
Provider
POST - Recovery
If you would like to resend all the odds for all events you can use to following POST API data
for the specified product which will send odds_change messages in the queue.
Endpoint
Method
Input Body
Sample Request Body
/api/v1/recovery
POST
Product ID
The response Body should be as follows:
<?xml version='1.0' encoding='utf-8'?>
<response timestamp="1673531781" response_code="ACCEPTED"/>