You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
This type of message is sent through AMQP service when result of outcome is known
Message structure
| .message |
|
|---|
| id |
|
| type | outcome_result |
| 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 |
|
|---|
| ...outcome_result |
|
|---|
| id | Identifier of the outcome
|
| betting_offer_id | Identifier of the betting_offer. The complete list of possible betting_offer can be retrieved using the API resource: betting-offers.index |
| action | Describes type of operation for the event. Possible values: - insert - new event generated
- update - event was updated
- delete - event was deleted
|
| status | 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
|
| result | Possible values:
- won - user won his bet, user should receive winnings (odds*stake)
- 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 (odds*stake/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. |
|
|