The matcher is not healthy
The order itself has been accepted, but at least one (possibly all) actions have generated errors
There is an error with an action that has caused the entire order to be rejected. Check the instructionReports errorCode for the reason for the rejection of the order.
Order rejected due to the account's status (suspended, inactive, dup cards)
Order rejected due to the account's wallet's status
Account has exceeded its exposure limit or available to bet limit
The account has exceed the self imposed loss limit
Market is suspended
Market is not open for betting. It is either not yet active, suspended or closed awaiting settlement.
Duplicate customer reference data submitted - Please note: There is a time window associated with the de-duplication of duplicate submissions which is 60 second
Order cannot be accepted by the matcher due to the combination of actions. For example, bets being edited are not on the same market, or order includes both edits and placement
Market doesn't exist
Business rules do not allow order to be placed. You are either attempting to place the order using a Delayed Application Key or from a restricted jurisdiction (i.e. USA)
duplicate bet ids found
Order hasn't been passed to matcher as system detected there will be no state change
The requested service is unavailable
The regulator rejected the order. On the Italian Exchange this error will occur if more than 50 bets are sent in a single placeOrders request.
|NO_CHASING||A specific error code that relates to Spanish Exchange markets only which indicates that the bet placed contravenes the Spanish regulatory rules relating to loss chasing.|
|REGULATOR_IS_NOT_AVAILABLE||The underlying regulator service is not available.|
|TOO_MANY_INSTRUCTIONS||The amount of orders exceeded the maximum amount allowed to be executed|
You may only specify a time in force on either the place request OR on individual limit order instructions (not both),
since the implied behaviors are incompatible.
You have specified a persistence type for a FILL_OR_KILL order, which is nonsensical because no umatched portion
can remain after the order has been placed.
You have specified a time in force of FILL_OR_KILL, but have included a non-LIMIT order type.
You have specified a minFillSize on a limit order, where the limit order's time in force is not FILL_OR_KILL.
Using minFillSize is not supported where the time in force of the request (as opposed to an order) is FILL_OR_KILL.