Orders and statuses

get_order returns the order, and order_updated pushes it without orderType, timeInForce, limitPrice, fills, mints, burns, fees and feeTotal. Every field is in the API reference.

{
  "orderId": "3396877",
  "regulatoryId": "ec6c1265-8dc2-4bca-8f67-2e6206e3f39b",
  "externalRef": "ref-2026-08-28-0001",
  "status": "PARTIALLY_FILLED",
  "brokerStatus": "PARTIALLY_FILLED",
  "side": "B",
  "symbol": "AAPL",
  "orderType": "LIMIT",
  "timeInForce": "DAY",
  "quantity": "10",
  "executedQuantity": "4",
  "leavesQuantity": "6",
  "limitPrice": "150.25",
  "executedPrice": "150.25",
  "currency": "USD",
  "createdAt": "2026-08-28T15:29:46.936Z"
}

Identifiers

Identifier	Set by	Use it for
`orderId`	Securitize, in the `ack`	`cancel_order` and `get_order`. Every order message takes it
`externalRef`	You, in `place_order`	Idempotency, and `get_order` when you have no `orderId`. It also starts every mint and burn memo
`regulatoryId`	The broker, once it acknowledges the order	Reporting and joining: it is the order’s id in regulatory (CAT) reporting, and it ties the order to its trades (`orderRegulatoryId`), mints and burns. Not for addressing the order

Record regulatoryId from the ack: it is there for that reason.

Quantities

Field	Meaning
`quantity`	Shares ordered
`executedQuantity`	Shares executed so far: the sum of the effective executions
`leavesQuantity`	Shares still working. The field to make decisions on: zero means nothing is left, and nothing to cancel

Unlike a status, leavesQuantity cannot arrive as a value you have no mapping for. The three are the broker’s arithmetic, passed through unchanged; if they do not reconcile, treat the order as a fault and contact Securitize with the traceId.

Fees

Every get_order answer carries fees, one per trade the order filled in, and feeTotal, their sum. A fee is charged when its trade reaches the broker’s ledger, which is after the fill, so the list can grow after the order has filled: read the order again rather than taking an empty list as final.

"fees": [
  {
    "transactionNo": "12874152.000000",
    "reference": "fee.12874152",
    "amount": "0.15",
    "perShare": "0.003",
    "status": "BOOKED",
    "chargedAt": "2026-08-28T15:30:03.112Z",
    "bookedAt": "2026-08-28T15:31:01.529Z"
  }
],
"feeTotal": "0.15"

`status`	Meaning
`PENDING`	Charged, and not booked by the broker yet. It books about a minute later
`BOOKED`	The transfer is on the broker’s ledger
`FAILED`	The transfer was refused or cancelled. The fee is still owed

feeTotal counts every status: it is what the order is charged. A trade too small to owe a cent at the rate carries no fee. Fees are not pushed: get_order is where they are read.

Limits on an order

Every order is placed by quantity. An order by notional answers INVALID_ORDER.
A buy is a LIMIT order paid from your own cash. quantity × limitPrice plus its fees is held against the available of get_cash_balance_v2 until the order fills or ends. A buy that cash does not cover, and a MARKET buy, answer INVALID_ORDER. See Your own cash.
The broker checks the account as a whole too: a buy it cannot pay for answers INVALID_ORDER with the message Insufficient buying power.
A sell the redemption wallet cannot cover is refused with INVALID_ORDER, and a sell must be placed by quantity. See Sell shares and redeem CETs.
The symbol is checked before the order is sent. A symbol your account does not trade, mistyped or not, answers INVALID_ORDER; check it against get_symbols. A symbol your account trades that the broker no longer recognises answers INVALID_SYMBOL naming it.
Decimal places: quantity 5, limitPrice 4.
Tick size: a limitPrice of 1.00 or more must be in whole cents, at most 2 decimal places. A finer price is refused by the broker as sub-penny (Risk validation: Sub-penny trading is not allowed). Only a price under 1.00 may use 4 decimal places.
limitPrice is required on a LIMIT order and refused on a MARKET one, which only a sell may be.
Only DAY is supported as timeInForce, and it is the default. IOC and FOK are not offered through the broker’s API and answer INVALID_ORDER. A GTC order is acknowledged and then refused by the broker, arriving as REJECTED.

Status

`status`	Meaning
`WORKING`	Live, nothing executed yet
`PARTIALLY_FILLED`	Some executed, the rest still working
`FILLED`	Fully executed. Final
`PENDING_CANCEL`	A cancellation was requested and is not confirmed yet
`CANCELLED`	Cancelled. Final. Shares executed before the cancellation stay executed
`REJECTED`	Not taken. Final
`EXPIRED`	Its time in force ran out. Final
`UNKNOWN`	The broker’s status has no mapping. `brokerStatus` has the original; trust the quantities

An update can skip states: an order can go from WORKING straight to FILLED. Treat the list as open. On a status you do not recognise, fall back to the quantities instead of failing; a status may be added. brokerStatus is the broker’s own code, for support conversations about one order; branch on status.

Get started

Sandbox only

Guides

Concepts

Help

API reference

Identifiers

Quantities

Fees

Limits on an order

Status