5.4 Statuses and Currencies

5.4.1 Bet statuses

The status field of a statement object, and the values accepted by the statuses filter on GET /bets/.

Status	Meaning
`accepted`	The bet has been successfully placed and accepted. Not settled yet.
`won`	The bet has been won.
`lost`	The bet has been lost.
`void`	The bet has been voided, for a reason that should ideally be provided.
`push`	A successful bet with profit and loss of zero — draw-no-bet, or an asian handicap that voids on some results.
`rejected`	The bet has been rejected, for a reason that should ideally be provided.
`danger`	The bet went through your system and is in danger for now. It should transition to a different state within moments.
`pending`	The bet went through your system and is queued for now. It should transition to a different state within moments.
`failed`	The bet went through your system but eventually failed, for a reason that should ideally be provided.

Two rules apply when reporting these:

Half outcomes collapse. In the case of half-win, half-lost or half-push, report simply won, lost or push.
Give a reason. Whenever a bet is failed, rejected or void, populate the reason field. Send null only if you genuinely have no reason to give.

danger and pending are transitional. Reporting either one causes the single-bet endpoint to be polled until the bet reaches a final state.

The status field of the response to POST /bets uses a narrower set:

Status	Meaning
`accepted`	The bet has been successfully placed.
`failed`	The bet failed to place.
`danger`	The bet is in danger.

The status field of GET /account:

Status	Meaning
`active`	The account is usable.
`disabled`	The account is not usable, and will not be traded against.

The ccy_code field, and the currency element of every currency amount, must be one of the following ISO 4217 codes:

AUD, CAD, CNH, DKK, EUR, GBP, HKD, IDR, INR, JPY, MXN, MYR, NZD, RUB, SGD, THB, TWD, USD, VND