Agara

Taker delay

Which orders wait before matching, what can change during the wait, and how to track the final outcome.

A taker delay is a minimum wait before an incoming order can trade against available liquidity. A taker order can match another trader's eligible quote immediately. A maker order can rest on the book without an immediate fill.

This delay applies to signed orders submitted through Order Service (/order/v1), including batches.

When an order waits

An order must first pass the usual trading checks. A delay does not make an invalid order valid.

Initial outcomeWhat you receiveWhat happens next
The order can rest without taking liquidityAn order state such as OPENThe order rests without a taker delay.
The order can take liquidity and its configured delay is greater than zeroHTTP 202 with status: "TAKE_ORDER_DELAY"The entire order waits before matching. No part fills or rests during this wait.
The configured delay is zeroThe normal placement resultThere is no added taker wait.
The order fails an initial checkA rejectionThe order does not enter the wait.

Eligible liquidity includes cross-orderbook matching. Your own orders do not count as executable liquidity for this check; self-trade prevention still applies.

How long the delay lasts

The delay depends on the market's configuration. A market setting overrides its event's primary-category setting; if neither is set, the global default applies. A setting can explicitly disable the wait, including when an inherited setting enables it. Orders already waiting keep their assigned delay.

The duration is an at-least wait, not a promise that execution or a response will arrive at that exact time. Agara measures the wait before allowing the order to proceed. Network transit and later processing can add time. Do not restart the countdown when the acknowledgement reaches your client.

When a delay applies:

  1. The order enters the wait and Agara returns TAKE_ORDER_DELAY.
  2. Before the assigned wait has elapsed, the order cannot fill or rest. Changes to the book do not release it early.
  3. After the full wait, the order can proceed against the book and available funds at that time.
  4. Account events and order reads report the resulting fills, resting order or rejection.

What can change during the wait

The waiting order is not on the book and does not reserve cash, shares or the initially available liquidity. Other orders can use those resources. Existing resting orders remain tradable and cancellable.

Prices and available quantity can change. Your original price limit still applies, but the initial quote and fill quantity are not guaranteed. If other orders use your funds or shares, or the market closes, the waiting order can be rejected when it proceeds.

You cannot cancel or edit an order while it waits. A cancellation attempt returns HTTP 409 with code: "order_not_cancellable". Cancel-all removes resting orders; it does not remove waiting orders. Once a delayed order has rested, you can cancel its unfilled remainder normally.

What each order type can do

The order keeps its original time in force after the wait.

Order typeExpected behaviour
GTCCan fill fully, fill partly and rest, or rest without a fill if the eligible liquidity has disappeared.
GTDBehaves like GTC until its original expiry. The delay does not extend that expiry; an order that expires during the wait can be rejected when it proceeds.
FAKIf initially eligible to trade, waits before filling the available quantity and cancelling any remainder. With no executable liquidity initially, it is rejected without waiting. With none after the wait, it is rejected without a fill.
FOKIf initially fillable in full, can wait. After the wait it must still fill in full or be rejected with no partial fill. An initially unfillable FOK is rejected without waiting.
Post-onlyA valid maker can rest without waiting. An order that would take another trader's liquidity is rejected, rather than delayed until it becomes a maker.

Example: a taker becomes a maker

You submit a GTC BUY for 10 shares at 0.60 while another trader has shares offered at 0.60. The order receives a taker delay. That trader cancels their offer during the wait, and no other eligible liquidity remains.

Your order still completes the full wait. It can then rest as a BUY at 0.60, assuming the other trading checks still pass. It does not rest early when the offer disappears.

Track the final outcome

The HTTP 202 response completes the placement request. The final outcome is reported separately through account events and order reads; there is no second HTTP response to the original request.

Keep the exact signed request, its hash and the returned order ID. A batch item uses outcome: "delayed" with status: "TAKE_ORDER_DELAY". Treat that as waiting, not as a confirmed fill or resting order. Retrying the same order while it is still waiting does not shorten its delay or create another waiting copy.

Record order_rejected events even if a later lookup returns HTTP 404 with code: "order_not_found". Some orders rejected after the wait are not available through subsequent order reads. A missing lookup does not undo an event you already received.

Waiting orders can be lost during a service interruption before matching. After an interruption, reconcile the original order's events and reads before retrying or replacing it. Retrying the same signed request may start a new wait; an earlier acknowledgement does not guarantee automatic execution after recovery.

See managing delayed orders for the client workflow and Orders - New for request and response fields.