Betting Status

Betting status

get

Lists all possible betting statuses.

Authorizations
Responses
200

successful operation

application/xml
get
GET /v1/descriptions/betting_status.xml HTTP/1.1
Host: global.api.betradar.com
x-access-token: YOUR_API_KEY
Accept: */*
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<betting_status_descriptions response_code="OK">
  <betting_status id="0" description="UNKNOWN"/>
  <betting_status id="1" description="GOAL"/>
  <betting_status id="2" description="DANGEROUS_FREE_KICK"/>
  <betting_status id="3" description="DANGEROUS_GOAL_POSITION"/>
  <betting_status id="4" description="POSSIBLE_BOUNDARY"/>
  <betting_status id="5" description="POSSIBLE_CHECKOUT"/>
  <betting_status id="6" description="INGAME_PENALTY"/>
</betting_status_descriptions>

About the Endpoint

Endpoint PATH

/descriptions/betting_status.xml

Endpoint Description

This endpoint returns a list of all possible betting statuses (in odds_changes.odds).

Note: The betting status description is only sent when (if) the Live Odds producer is in early betstart.

Endpoint Parameters

Not needed.

Endpoint Structure

  • <betting_status_descriptions>

    • <betting_status>

XML Example

Request URL

https://api.betradar.com/v1/descriptions/betting_status.xml

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <betting_status_descriptions response_code="OK">
    <betting_status id="0" description="UNKNOWN"/>
    <betting_status id="1" description="GOAL"/>
    <betting_status id="2" description="DANGEROUS_FREE_KICK"/>
    <betting_status id="3" description="DANGEROUS_GOAL_POSITION"/>
    <betting_status id="4" description="POSSIBLE_BOUNDARY"/>
    <betting_status id="5" description="POSSIBLE_CHECKOUT"/>
    <betting_status id="6" description="INGAME_PENALTY"/>
  </betting_status_descriptions>

Last updated

Was this helpful?