POST /v1/orders both previews and places. mode is required and has no default, so a request can never place by accident.
The request
How the stake is split
The stake is split across the requested bookmakers that offer a price at or aboveminPrice, within each one’s limits. Each part becomes a bet. An order can therefore have several bets, at different prices; averageFilledPrice is their stake-weighted average.
Partial fills and expiry
An order with
expiresAt stays working until it fills or expires. Cancel it early with POST /v1/orders/{id}/cancel. Some environments do not offer expiry yet: they answer 503 EXPIRY_NOT_AVAILABLE, and the same order without expiresAt works.
Bookmakers
- Your bookmakers.
GET /v1/melists the bookmakers of your account. Asking for another one answers403 BOOKMAKER_NOT_AVAILABLE. - Bookmakers closed to the API. A bookmaker can be closed to the API even when it is enabled on your account, and
GET /v1/meleaves it out. Asking for it answers400 BOOKMAKER_NOT_AVAILABLE_VIA_API, and it is never used whenbookmakersis omitted.
Preview first
A preview answers with what would be placed now: one entry per bookmaker inbets, with its status, stake and price.
GET /v1/betslip: see Feed odds and the betslip.
Rejections
Before anything is sent to a bookmaker, the order is checked: your balance, your limit per fixture, your account’s rules, the prices and the liquidity. When a check fails, the request answers an error and nothing is recorded; see Errors. Once the order is recorded, a bookmaker can still decline its part. That is not an error: the order comes back, and the declined bet hasstatus: "REJECTED" and a declineReason. See Order and bet life cycle.