This type of message is sent through AMQP service when a new betting offer should be created or some part of betting offer (e.g. odds) are updated. The message include all betting offer information and related outcomes.
Message structure
| .message | |
|---|---|
| id | Unique identifier for the message |
| type | betting_offer |
| source | Internal attribute, please dont use this attribute |
| ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP |
| ..data | |
| ...betting_offer | |
| id | Identifier of the betting offer |
| action | Describes type of operation for the betting offer. Possible values:
|
| bookmaker_id | Identifier of the bookmaker assigned to you during subscription purchase |
| is_live_offer | Possible values:
|
| market_id | Identifier for the market. The complete list of possible markets and their default market can be retrieved using the API resource: markets.index |
| market_name | Name of the market |
| object_type | Possible object type:
|
| object_name | Name of the object e.g: Barcelona - Real Madrid or Premiership 2015/16 |
| sport_id | Unique identifier for the sport. The complete list of possible sports can be retrieved using the API resource: sports.index |
| area_id | Unique identifier for the area. The complete list of possible areas can be retrieved using the API resource: areas.index |
| competition_id | Unique identifier for the competition. The complete list of possible competitions can be retrieved using the API resource: competitions.index |
| season_id | Unique identifier for the season. The complete list of possible seasons can be retrieved using the API resource: seasons.index |
| event_id | Unique identifier for the event. The complete list of possible events can be retrieved using the API resource: events.index |
| event_status_id | Unique identifier of the event status. Available only when object_type=event, in other cases null value |
| event_result | Result for the event in format result1:result2 e.g: 2:0. For some sports like tennis attribute will contain results of each period seperated by | e.g 1:1| 4:5 |15:0 Available only when object_type=event and for an event with 2 participants, in other cases null value |
| clock_status | Clock status. Possible value:
|
| clock_time | How many seconds have passed in the current event period. Available only when object_type=event, in other cases null value |
| replacer | For some markets we are using replacers. It's a list of key=value atributtes seperated by | e.g. participant1=Barcelona | participant2=Real. The complete list of possible replacers for each market can be retrieved using the API resource: markets.index. Possible null value. |
| status | Possible values:
|
| display_order | The parameter used to sort betting offers. Sorting direction is ascending |
| start_date | Date when the betting offer starts in format DATE_TIME (2015-03-01 11:02) |
| open_at | Date when the betting offer was opened in format DATE_TIME (2015-03-01 11:02) |
| closed_at | Date when the betting offer should be closed in format DATE_TIME (2015-03-01 11:02) |
| ....outcomes | |
| .....outcome | |
| id | Identifier of the outcome |
| default_outcome_id | Default outcome id. The complete list of possible default outcomes can be retrieved using the API resource: default-outcomes.index |
| name | Name of the outcome |
| participant_id | Identifier of the participant related to the outcome. Possible null value. The complete list of possible participants can be retrieved using the API resource: participants.index |
| status | Possible values:
|
| result | Possible values:
Possible empty value for outcomes yet to be settled. |
| starting_odds | The starting odds offered by the bookmaker in decimal format |
| odds | The current odds offered by the bookmaker in decimal format |
| probability | Probability of the outcome in format 0.65 |
| display_order | The parameter used to sort outcomes. Sorting direction is ascending |