Skip to main content
Every error response has the same shape:
Most rejections happen before the order reaches the book, so a 400 means nothing was placed.
markets-service verifies your signature at submission — see Authentication and signing. An order whose signature does not authorize its action is rejected here rather than failing later onchain.

Custody

400
The Matching contract does not hold this subaccount. Deposit it first. The same applies to subaccount_id … has no owner recorded in matching.
503
A chain read failed, so the venue cannot yet say whether it holds the subaccount. Nothing is wrong with the order. Resubmit it.

Signature

400
The signature did not recover to signer_address, and the signer is not a contract whose isValidSignature accepted it.The digest is over the Action struct exactly as described in Authentication and signing — domain Matching version 1.0, bound to the chain and the Matching contract. A mismatch in any signed field produces a different digest and so a different recovered address. Check that action_json is byte-for-byte what you signed, and that signer_address is the key that signed it rather than the account that owns it.
A signature that cannot be checked — for example an RPC failure while resolving a contract signer — is not a rejection. The order is accepted and the failure is logged, so a transient outage never blocks a valid order.

Missing fields

Every one of these is required on POST /orders.

Action payload shape

These come from decoding action_json.data, the ABI-encoded TradeData tuple.
400
data is not exactly seven 32-byte words. After the 0x prefix it must be 448 hex characters. See Encoding data.
400
data is the right length but not valid hex.
400
A wrapper around the field-level failures below. The suffix names the specific problem.

Field consistency

The flat order fields and the signed action_json describe the same order, so they must agree. Rebuild both from one set of values rather than editing one of them.

Scaling

These are the most common rejections, and they almost always mean the body was sent in wei.
400
data.limitPrice must be a positive whole multiple of the body’s limit_price after tick normalization. The body takes human decimals; only data carries wei.
400
Same rule for size, normalized against the instrument’s minimum size.
400
limitPrice is a signed int256 but zero and negative values are rejected.
400
Same for desiredAmount.
400
desired_amount is smaller than the instrument’s minimum size, so it normalizes to nothing.
400
desired_amount is not a whole multiple of the instrument’s minimum size.
If a price or amount error appears and the numbers look correct, check the scale first. See Price and amount use two different scales.

Amounts and expiry

Instrument

400
The (asset_address, sub_id) pair is not an enabled market. Read GET /markets — both values must come from the same entry.
400
GET /book, GET /trades and GET /candles refuse a request that does not name a listed market. The body carries the error code, a message, and the identifiers the venue accepts:
Two messages occur. no such market: <identifier> means the symbol, or the asset_address + sub_id pair, matched nothing: identifiers match exactly, with no prefix or case folding. A delisted market, such as cNGN-USDC and EURC-USDC (spot, delisted 2026-11-19), matches nothing. symbol or asset_address is required means the request named no market at all.
400
Every listed market is a future, and futures take raw engine values. Omit both fields.

Duplicate orders

409
order_id has already been submitted. Generate a fresh one; do not retry with the same id.
Treat order_id as an idempotency key you control. A 409 means the first submission was accepted, so check its status with GET /orders/{order_id} rather than resubmitting.

Cancelling

Read endpoints

unknown_market applies to GET /book, GET /trades, and GET /candles alike, and is the one error on those endpoints whose body carries more than error.

Authentication and signing

Most rejections trace back to how the action payload was built.