One Trading API
REST APIWebSocket API
REST APIWebSocket API
  1. Account
  • Introduction
  • Authenticate
  • Subscribe
  • Ping / Pong
  • Trading
    • Introduction
    • Create Order
    • Cancel All Orders
    • Cancel Order by Client ID
    • Cancel Order by Order ID
    • Margin Update
    • Settlement
    • Funding Payment
    • Order Booked
    • Order Rejected
    • Order Closed
    • Trade Executed
    • Order Fully Filled
    • Move Order
    • Balance Adjustment
  • Orderbook
    • Introduction
    • Orderbook Snapshot
    • Orderbook Update
  • Price Ticks
    • Introduction
    • Price Tick
  • Book Ticker
    • Introduction
    • Book Tick
  • Mark Price
    • Mark Price Update
    • Introduction
  • Account
    • Introduction
    • Exotic Order Registered
    • Exotic Order Updated
    • Exotic Order Activated
    • Exotic Order Triggered
    • Exotic Order Executed
    • Exotic Order Cancelled
  1. Account

Introduction

The ACCOUNT WebSocket channel sends events about your account, such as the changes of state of your take profit / stop loss orders (TP/SLs).
One subscription covers your main account and every subaccount. Each message carries the account_id it belongs to.
Note
You must authenticate before subscribing.

Subscribe#

{
    "type": "SUBSCRIBE",
    "channels": [
        {
            "name": "ACCOUNT"
        }
    ]
}

Subscription Confirmation#

{
    "type": "SUBSCRIPTIONS",
    "channels": [
        {
            "name": "ACCOUNT",
            "account_id": "726288e6-a463-4f88-9068-024ae8f97a34"
        }
    ],
    "time": 1763288100299000000
}
The channel sends no snapshot, and messages are not replayed after a reconnect.

Message format#

Every message on the channel carries these fields:
FieldTypeDescription
channel_namestringACCOUNT.
typestringThe kind of event: see Message types. The rest of the message depends on it.
timestringWhen the message was sent, as an ISO 8601 string.
account_idstringThe account the event belongs to: your main account, or one of its subaccounts.

Message types#

typeSent when
EXOTIC_ORDERA take profit / stop loss (TP/SL) was created, armed, changed, triggered, executed or cancelled.
More types may be added: ignore a type you do not recognise.

Take profit / stop loss (EXOTIC_ORDER)#

A TP/SL is held in a separate service, not on the exchange itself, so it does not appear on the TRADING channel. When one of its levels is reached, the close orders it places are ordinary orders: they and their trades are reported on that channel.
An EXOTIC_ORDER message adds the event and the TP/SL to the common fields:
{
    "channel_name": "ACCOUNT",
    "type": "EXOTIC_ORDER",
    "time": "2026-11-16T10:15:02.512Z",
    "account_id": "726288e6-a463-4f88-9068-024ae8f97a34",
    "event_type": "EXOTIC_ORDER_ACTIVATED",
    "event_timestamp": "2026-11-16T10:15:02.000Z",
    "data": {
        "version": 2,
        "client_id": "0d0b1f0c-7f0e-4f55-9a53-6f6f3c1c2a10",
        "status": "ACTIVE",
        "…": "…"
    }
}
FieldTypeDescription
event_typestringWhat happened to the TP/SL: see the table below.
event_timestampstringWhen it happened (ISO 8601). Use it to put messages in order.
message_idstringEXOTIC_ORDER_TRIGGERED only. That message can be delivered more than once with the same message_id: deduplicate on it.
dataobjectThe TP/SL, in the shape of its event_type. Always carries "version": 2.
event_typeSent when
EXOTIC_ORDER_REGISTEREDA TP/SL was created
EXOTIC_ORDER_UPDATEDIts levels were changed
EXOTIC_ORDER_ACTIVATEDIt became ACTIVE: its levels are being watched
EXOTIC_ORDER_TRIGGEREDA level was reached and its close is about to be placed
EXOTIC_ORDER_EXECUTEDIts close finished
EXOTIC_ORDER_CANCELLEDIt ended without completing a close, with the reason
To read the current state, for example after a reconnect, use Get Exotic Orders (TP/SL).

Lifecycle#

PENDING ──→ ACTIVE ──→ TRIGGERED ──→ COMPLETE
  │           │           │
  └───────────┴───────────┴──────────→ CANCELLED
TransitionMessage
CreatedEXOTIC_ORDER_REGISTERED
PENDING → ACTIVE, or straight away for a position TP/SL created on an open positionEXOTIC_ORDER_ACTIVATED
Levels changedEXOTIC_ORDER_UPDATED
ACTIVE → TRIGGEREDEXOTIC_ORDER_TRIGGERED
TRIGGERED → COMPLETEEXOTIC_ORDER_EXECUTED
Any → CANCELLEDEXOTIC_ORDER_CANCELLED
data.status is the TP/SL's status after the event. Levels are sent as numbers (take_profit_price, trigger_price); amounts are decimal strings.
Previous
Introduction
Next
Exotic Order Registered
Built with