Skip to main content
An order can be rejected at intake — before it ever becomes a resting quote on the book — for a handful of well-defined reasons. This page lists them, explains what each one means, and gives you the single sentence you need to fix it. If you are seeing an unfamiliar error string, match it against the list below. For every case there is a specific docs page linked that goes into the details; this page is the index, not the authoritative reference.

​
Tick or lot size violation

What it means. The order’s price is not a multiple of the instrument’s tick size, or the quantity is not a multiple of the lot size. Intention enforces both constraints strictly so that the book uses integer ticks and integer lots in the matching path. Remedy. Round the price to the tick and the size to the lot. See Precision for the authoritative values and the rounding direction the API expects.

​
Notional below the minimum

What it means. The order’s notional value — price times quantity — is below the minimum allowed for that market. Very small orders are rejected because they waste space on the book without contributing liquidity. Remedy. Increase the order size until the notional clears the minimum for that market.

​
Leverage above the tier ladder for that position size

What it means. Intention uses a tier ladder: larger positions require more margin per unit of notional. If an incoming order would push your position into a tier whose max leverage is lower than the leverage you are currently using, the order is rejected. Remedy. Either reduce the order size, or add margin to your account so the resulting position sits within an allowed tier. See Leverage for the full ladder.

​
Per-address or per-IP rate limit

What it means. You are submitting messages faster than the documented limit for the relevant scope. The rate limits exist to keep the network usable under load and to prevent a single actor from monopolizing intake capacity. Remedy. Slow down. If you are a market maker running into these limits under normal operation, email contact@intention.xyz about a builder-code integration.

​
Open-interest limit

What it means. The market has a cap on total open interest, and your order, if filled, would push the aggregate over that cap. Open-interest limits protect the insurance fund from concentration risk during fast moves. Remedy. Wait for aggregate OI to decrease, or size down. See OI limits.

​
Reduce-only flag would increase position

What it means. You submitted the order with the reduce-only flag set, but the order, if it were filled, would grow your position instead of shrinking it. Intake refuses the order rather than silently flipping the flag off. Remedy. Either remove the reduce-only flag, or invert the side so that it does reduce your position. See Reduce-only.

​
Something else

If the rejection reason does not match any of the above — and in particular if the error is a generic “internal” or “unknown” code — capture the full API response, the order payload, and the UTC time, and send them to support@intention.xyz. Also review Order types to make sure the combination of flags you are sending is valid for the order type you chose.