Page Comparison

This type of message is sent through AMQP service when particular betting offer should be cancelled and refunded due to an error.

Message structure

Possible values:

yes - in-play betting offer
no - prematch betting offer *

* If live odds are going to be available for the event one minute before the event start date we will change this attribute from „no” to „yes”. If we don't offer live odds for the event all betting offers will be closed at this moment.Possible values:

active - outcome and odds are displayed, user can make bets. Default value for new outcome

suspended - outcome is suspended, user can't make bets

closed - outcome is closed and will be not offer it the future, user can't make bets

resulted - outcome has result (result attribute is not empty)

cancelled - outcome is cancelled

.message
id	Unique identifier for the message
type	betting_offer_cancelrollback
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_cancel
id	Identifier of the betting offer
action	Describes type of operation for the event. Possible values: insert - new betting_offer_cancel offer generated update - betting offer was updated
bookmaker_id	Identifier of the bookmaker assigned to you during subscription purchase
is_live_offer
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: season event
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 The complete list of possible events statuses can be retrieved using the API resource: statuses.index
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: running stopped Available only when object_type=event, in other cases null 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: active - the odds are published and users can make bets. Defaut value for new betting offer suspended - the users can't bet on the betting offer (e.g when team received the red card) closed - the betting offer is closed and no further bets will be taken cancelled - the betting offer is cancelled
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 when a previously sent information concering particulat betting offer was incorrect. It could be happen when our operator made a mistake and cancel incorrect betting offer
betting_offer_id	Identifier of the betting_offer. The complete list of possible betting_offer can be retrieved using the API resource: defaultbetting-outcomesoffers.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
result	Possible values: won - user won his bet, user should receive winnings (oddsstake) lost - user lost his bet, user lost his stake void - user should receive his stake back partial win - user won part of his bet, user should receive winnings (oddsstake/2 + stake/2) partial loss - user lost part of his bet, user should receive half of his stake back 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 ascendingstart_date	If specified it means a start date from which all bets made should be cancelled. Possible empty value
end_date	If specified it means an end date to which all bets made should be cancelled. Possible empty value

Versions Compared

Old Version 2

New Version Current

Key

Message structure