Order Lifecycle

This page describes the states an order passes through from creation to completion, and maps them to the numeric status codes returned in REST responses and WebSocket notifications.

---

Order States

                    ┌─────────────┐
        ┌──────────▸│  INSERTED   │──────────────┐
        │           │  (status 2) │              │
        │           └──────┬──────┘              │
        │                  │                     │
        │                  ▼                     ▼
        │        ┌─────────────────┐    ┌──────────────────┐
  Place │        │    PARTIALLY    │    │      FULLY       │
  Order │        │    FILLED       │    │    TRANSACTED     │
        │        │   (status 5)   │    │    (status 4)     │
        │        └────────┬───────┘    └──────────────────┘
        │                 │
        │                 ▼
        │       ┌──────────────────┐
        │       │    CANCELLED     │
        │       │   (status 6)    │
        │       └──────────────────┘
        │
        ▼
  ┌──────────────┐          ┌──────────────────┐
  │   REJECTED   │          │     TIMEOUT      │
  │  (status 15) │          │   (status -1)    │
  └──────────────┘          └──────────────────┘

---

Status Codes

Status	Constant	Description	Terminal?
-1	TIMEOUT	Request timed out — the order may or may not have been placed. Query the order to confirm.	No
2	ORDER_INSERTED	Order accepted and resting on the orderbook	No
4	ORDER_FULLY_TRANSACTED	Order completely filled	Yes
5	ORDER_PARTIALLY_TRANSACTED	Order partially filled — remaining size still resting	No
6	ORDER_CANCELLED	Order cancelled (by user, system, or expiry)	Yes
7	ORDER_REFUNDED	Order refunded	Yes
8	INSUFFICIENT_BALANCE	Rejected — not enough funds	Yes
9	TRIGGER_INSERTED	Trigger/stop order accepted — waiting for trigger condition	No
10	TRIGGER_ACTIVATED	Trigger condition met — order converted to limit/market	No
15	ORDER_REJECTED	Order rejected (invalid params, risk limits, etc.)	Yes
65	STATUS_ACTIVE	Order is active	No
85	STATUS_PROCESSING	Order is being processed	No
88	STATUS_INACTIVE	Order is inactive	Yes
123	AMEND_ORDER	Order amended successfully	No

See Error Codes for the full enum table.

---

Typical Flows

Limit order — fully filled

Place order → status 2 (INSERTED) → status 4 (FULLY_TRANSACTED)

Limit order — partial fill then cancel

Place order → status 2 (INSERTED) → status 5 (PARTIALLY_TRANSACTED)
             → Cancel request → status 6 (CANCELLED)

Market order — immediate fill

Place order → status 4 (FULLY_TRANSACTED)

Market orders are usually filled immediately. You may not see status 2.

Stop/trigger order

Place order → status 9 (TRIGGER_INSERTED)
             → Price hits trigger → status 10 (TRIGGER_ACTIVATED)
             → status 2 (INSERTED) → status 4 or 5 (filled)

Rejected order

Place order → status 15 (REJECTED) or status 8 (INSUFFICIENT_BALANCE)

Check the message field in the response for the rejection reason.

Timeout

Place order → status -1 (TIMEOUT)

The order may or may not have been placed. Always query the order by clOrderID or orderID to confirm the actual state.

---

Tracking Orders in Real-Time

Use the WebSocket notificationApiV3 topic (Spot) or notificationApiV4 topic (Futures) to receive status updates as they happen:

{
  "topic": "notificationApiV3",
  "data": {
    "symbol": "BTC-USD",
    "orderID": "990db9b6-...",
    "status": 5,
    "filledBaseSize": 0.5,
    "totalFilledBaseSize": 0.5,
    "remainingBaseSize": 0.5,
    "avgFilledPrice": 36000.0
  }
}

Recommended approach:

1. Place order via REST — save the orderID
2. Listen on notificationApiV3 for status updates matching your orderID
3. When status is 4 (fully filled) or 6 (cancelled), the order is terminal

See WebSocket Guide for connection setup and Quickstart → Step 4 for code examples.

---

Order Type Codes

These numeric type codes appear in orderType fields:

Code	Type
76	Limit
77	Market
80	Peg / Algo
81	OTC