TICKERALL!
Developer reference

TickerAll API Docs

Everything you need to connect a broker account and trade it from your own code — REST endpoints, the realtime WebSocket, authentication, and copy-paste examples in curl, TypeScript, and Python.

Overview

TickerAll is a hosted API for connecting to and automating your own MT4/MT5 broker accounts. You write your strategy in any language; we hold a fast, persistent connection straight to your broker and keep it live for you, exposed over a clean REST + WebSocket API — so there's no MT4/MT5 terminal in the path, no EA bridge to wire up, and no reconnect churn when your strategy needs it.

The API has two planes:

REST control + data plane

https://api.tickerall.com

Connect accounts, read balance and positions, list symbols, and place / close / modify orders. Standard JSON over HTTPS.

Realtime data plane

wss://api.tickerall.com

A single long-lived WebSocket streams live ticks, position updates, and account updates as they happen.

One API key can hold many broker accounts at once — each scoped by its accountId. Symbol names are pass-through: you see the broker’s native names (e.g. EURUSD, BTCUSD), with no remapping. Prefer a typed client over raw HTTP? Grab the official SDKs linked at the top — TypeScript and Python, both wrapping this same REST + WebSocket API.

Authentication

Every request authenticates with a TickerAll API key sent as a bearer token. Sign up, open API keys in your dashboard, and create a key — it looks like cf_api_…. Treat it like a password; it carries the access of your whole account.

HTTP header
Authorization: Bearer cf_api_xxxxxxxxxxxxxxxxxxxx

Send this header on every REST call. For the WebSocket, send the same header on the upgrade request, or pass ?token=<key> in the URL where headers are awkward (e.g. browser clients).

A missing or invalid key returns 401 UNAUTHORIZED. Keys are validated on our side; revoking a key from the dashboard takes effect within a few minutes.

Read-only keys. When creating a key you can mark it Read-only — a data-only credential that reads candles, symbols, accounts, and history but is rejected with 403 FORBIDDEN on any trade or account mutation. Ideal for backtesting, analytics, or any integration that should never place orders. A full (default) key can trade.

Quickstart

From zero to a live order in four calls — then, on Pro, fan the same actions out across every account at once (step 5). Each step builds on the last. Prefer to click through it first? The dashboard's Test panel runs every one of these calls from your browser — no code.

01

Connect a broker account

POST your broker credentials to /v1/sessions. We authenticate against the broker and return an accountId. Your password is held in memory only while your connection is live, never saved to disk.

curl -X POST https://api.tickerall.com/v1/sessions \
  -H "Authorization: Bearer cf_api_xxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "broker": "mt5",
    "server": "Exness-MT5Trial14",
    "account": 12345678,
    "password": "your-broker-password",
    "terminalType": "MOBILE"
  }'
# terminalType is optional — "MOBILE" (default), "WEB", or "CLIENT" (desktop terminal). WEB/CLIENT require Pro or Enterprise.

# => { "accountId": "acc_8Kd3...", "isDemo": true, "status": "connected", ... }
02

Read account state

Use the accountId to read balance, equity, and open positions.

curl https://api.tickerall.com/v1/accounts/acc_8Kd3... \
  -H "Authorization: Bearer cf_api_xxxx"

# => { "status": "online", "account": { "balance": 9871.42, ... }, "positions": [...] }
03

Place and close an order

State-changing calls require an Idempotency-Key header — a unique string per logical action, so a retried request never double-fires.

# Open a 0.10-lot BUY market order (note the unique Idempotency-Key)
curl -X POST https://api.tickerall.com/v1/accounts/acc_8Kd3.../orders \
  -H "Authorization: Bearer cf_api_xxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{ "type": "market", "symbol": "BTCUSD", "side": "BUY",
        "volume": 0.10, "stopLoss": 71000, "takeProfit": 84000 }'
# => { "ticket": 4072808150, "status": "open", ... }

# Close it (ticket from the response above)
curl -X DELETE https://api.tickerall.com/v1/accounts/acc_8Kd3.../positions/4072808150 \
  -H "Authorization: Bearer cf_api_xxxx" \
  -H "Idempotency-Key: $(uuidgen)"
# => { "ticket": 4072808150, "closed": true, ... }
04

Stream live ticks

Open the WebSocket and subscribe to the symbols you care about.

# curl can't speak WebSocket; use websocat (or any WS client).
# Install websocat: brew install websocat | cargo install websocat | apt install websocat
websocat "wss://api.tickerall.com/v1/stream?token=cf_api_xxxx"

# then paste a subscribe frame:
{"type":"subscribe","channels":[{"kind":"ticks","accountId":"acc_8Kd3...","symbols":["BTCUSD"]}]}

# server streams:
# {"type":"tick","symbol":"BTCUSD","bid":77512.73,"ask":77514.10,"timestamp":"..."}
05

Execute across accounts (Pro)

Run the same action over many accounts in one call, then read all their state at once. Every bulk call reports each account's outcome separately, so a partial success is clear. Requires a Pro or Enterprise plan.

# Place the same 0.10-lot BUY across TWO accounts in one call (Pro/Enterprise)
curl -X POST https://api.tickerall.com/v1/bulk/orders \
  -H "Authorization: Bearer cf_api_xxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{ "orders": [
        { "accountId": "acc_8Kd3...", "symbol": "BTCUSD", "side": "BUY", "volume": 0.10 },
        { "accountId": "acc_9Lm4...", "symbol": "BTCUSD", "side": "BUY", "volume": 0.10 }
      ] }'
# => { "results": [ { "accountId": "acc_8Kd3...", "status": "filled", ... }, ... ],
#      "summary": { "total": 2, "filled": 2, "failed": 0 } }

# Read live state for many accounts in one call
curl "https://api.tickerall.com/v1/bulk/accounts?ids=acc_8Kd3...,acc_9Lm4..." \
  -H "Authorization: Bearer cf_api_xxxx"
# => { "accounts": [ { "id": "acc_8Kd3...", "status": "online", ... }, ... ],
#      "summary": { "total": 2, "online": 2, "offline": 0 } }

Postman & Insomnia

Prefer a GUI client? Import a ready-made collection — every REST endpoint below, with the Authorization bearer token wired up, an auto-generated Idempotency-Key on every write, example request bodies, and an example response on each call. Set two variables and start sending. Download the file, or use the Copy to clipboard option and paste it straight into the app.

PostmanInsomnia

Use the Download ▾ menu to switch between saving the .json file and Copy to clipboard — then paste it straight into Postman or Insomnia, no file needed.

Postman
  1. Import → drop in the file, or Raw text → paste the copied JSON.
  2. Open the collection’s Variables and set apiKey to your cf_api_… key.
  3. Run Open a broker session, then set accountId (and ticket once you have one).
Insomnia
  1. ImportFrom File, or From Clipboard after copying.
  2. Open Manage Environments and set apiKey, then accountId.
  3. The realtime feed is included as a ready WebSocket request.

baseUrl and wsBaseUrl come pre-filled. The WebSocket connect URL and subscribe frame are bundled in too — as a runnable request in Insomnia, and documented in the WebSocket (realtime) folder in Postman.

Conventions

Base URLs

REST: https://api.tickerall.com · WebSocket: wss://api.tickerall.com/v1/stream

Content type

Request and response bodies are JSON. Send Content-Type: application/json on calls with a body.

Idempotency-Key (required on writes)

Every state-changing call (POST orders, DELETE / PATCH positions) requires an Idempotency-Key: <unique-string> header. We store (key → response) for 24 hours; resending the same key replays the original response without re-executing. Omitting the header is a VALIDATION_ERROR. Use a fresh UUID per logical action.

Timestamps & numbers

Timestamps are ISO-8601 UTC strings. Tickets are integers. Prices and volumes are JSON numbers (lots for volume, e.g. 0.10).

Connection warmth

We keep a broker connection “hot” for a window after you start a session. If it cools, calls return 409 BROKER_ACCOUNT_NOT_HOT — just POST /v1/sessions again to re-warm it.

Sessions

A session is a warm, authenticated connection to one broker account. Start one to get an accountId; delete it to disconnect.

POST/v1/sessions

Connect a broker account. We authenticate and warm a live connection, then hand back an accountId — the handle for THIS broker connection. One API key can hold several broker accounts, so the id lives in this response (and in GET /v1/accounts), NOT in the key. Use it in every later /v1/accounts/:id call. Your password is held in memory only while the connection is live, never saved to disk.

Request body (JSON)
FieldTypeDescription
brokerreq"mt4" | "mt5"Which platform your broker server runs.
serverreqstringBroker server name, e.g. "Exness-MT5Trial14".
accountreqnumber | stringYour numeric broker login — the account number your broker assigns (e.g. 12345678). NOT your TickerAll email.
passwordreqstringBroker (investor or master) password. Used once to authenticate; never persisted.
terminalTypeoptional"MOBILE" | "WEB"Which client the connection presents AS — MOBILE (default) or WEB. Both expose the full surface (account, quotes, positions, history). Omit for MOBILE. Choosing WEB (or CLIENT) requires a Pro or Enterprise plan.
webTerminalUrloptionalstringThe broker’s web-terminal URL, e.g. https://mt5.yourbroker.com. REQUIRED when terminalType is "WEB" — web terminals are per-broker-domain, so the URL must be supplied. Ignored for MOBILE.
webEndpointoptionalstringAdvanced, optional: an explicit WebSocket endpoint override (e.g. wss://host/path) for the rare broker whose WS host/path differs from the webTerminalUrl derivation. Ignored for MOBILE.
200 OK
{
  "accountId": "acc_8Kd3...",
  "isDemo": true,
  "status": "connected",
  "expiresAt": "2026-05-22T18:42:10.000Z"
}
  • On the Free tier, only demo broker accounts are accepted — a real-money login is rejected with FREE_TIER_LIVE_REJECTED.
  • The connection stays warm for a while (see expiresAt). If it cools, calls return BROKER_ACCOUNT_NOT_HOT — just POST /v1/sessions again to reconnect.
DELETE/v1/sessions/:accountId

Disconnect a broker account and release its connection. Returns no body.

Path parameters
FieldTypeDescription
accountIdreqstringThe accountId returned by POST /v1/sessions.
204 No Content
(empty body)

Accounts

List your connected accounts, or fetch one account’s live financials and open positions.

GET/v1/accounts

List every broker account attached to your API key, with connection state.

200 OK
[
  {
    "id": "acc_8Kd3...",
    "broker": "mt5",
    "server": "Exness-MT5Trial14",
    "accountNumber": "****5678",
    "isDemo": true,
    "status": "CONNECTED",
    "hot": true,
    "lastHotAt": "2026-05-22T18:30:01.000Z",
    "createdAt": "2026-05-20T09:11:55.000Z"
  }
]
  • accountNumber is masked to the last 4 digits. hot=false means the connection cooled — POST /v1/sessions to re-warm it.
GET/v1/accounts/:id

Live account info — balance, equity, margin, leverage — plus the current open positions.

Path parameters
FieldTypeDescription
idreqstringaccountId.
200 OK (status: "online")
{
  "id": "acc_8Kd3...",
  "broker": "mt5",
  "server": "Exness-MT5Trial14",
  "accountNumber": "****5678",
  "isDemo": true,
  "status": "online",
  "account": {
    "name": "Demo Account 12345678",
    "accountType": "demo",
    "leverage": 500,
    "balance": 9871.42,
    "currency": "USD",
    "equity": 9863.10,
    "margin": 142.50,
    "freeMargin": 9720.60,
    "marginLevel": 6921.5
  },
  "positions": [
    {
      "ticket": 4072808150,
      "symbol": "BTCUSD",
      "side": "BUY",
      "volume": 0.10,
      "entryPrice": 77512.73,
      "stopLoss": 71000,
      "takeProfit": 84000,
      "currentPrice": 77640.10,
      "profit": 12.74,
      "swap": 0,
      "commission": 0,
      "comment": "my-strategy",
      "magic": 0,
      "openTime": "2026-05-22T17:55:03.000Z"
    }
  ]
}
  • If the connection has cooled, you get status:"offline" with a hint instead of live data — POST /v1/sessions to reconnect.
  • Money fields (equity, margin, freeMargin, marginLevel) may be null on an MT4 account that has not yet pushed a balance frame — null is honest "not available yet", never a misleading 0.
DELETE/v1/accounts/:id

Remove a broker account from your roster. We disconnect its live connection and drop it from your account list and from billing — this does NOT touch the broker account itself or any open positions. Reversible: reconnect the same login with POST /v1/sessions to re-add it.

Path parameters
FieldTypeDescription
idreqstringaccountId.
200 OK
{
  "id": "acc_8Kd3...",
  "status": "DISCONNECTED",
  "removed": true,
  "billableCount": 0
}
  • Idempotent — removing an already-removed account returns the same 200 shape.
  • If the account had always-hot enabled, that per-connection charge stops immediately; billableCount is your remaining always-hot connection count.
POST/v1/accounts/:id/migrateIdempotency-Key

Switch which terminal type the account presents AS ("MOBILE" or "WEB"). Your open positions, pending orders and balance live on the broker account, not the connection, so they are preserved across the switch.

Path parameters
FieldTypeDescription
idreqstringaccountId.
Request body (JSON)
FieldTypeDescription
toreq"MOBILE" | "WEB"The transport to switch to.
200 OK
{
  "id": "acc_8Kd3...",
  "terminalType": "MOBILE",
  "status": "noop"
}
  • status is "noop" when the account is already on the requested transport.
  • Switching runs only when the account is idle (no in-flight trade — otherwise 409).
  • Both terminal types expose the full surface (account, quotes, positions, history).
  • The switch is zero-gap — the new transport is warmed before the old session is dropped — so open positions, orders and balance carry over untouched.

Symbols

Discover the instruments you can trade on an account, in the broker’s native names.

GET/v1/accounts/:id/symbols

List tradeable symbols on the account, in the broker’s native names (pass-through, no normalization). symbols is the full catalog; watched is the subset that is actively streaming live ticks right now.

Path parameters
FieldTypeDescription
idreqstringaccountId.
200 OK
{
  "symbols": ["BTCUSD", "ETHUSD", "EURUSD", "GOLD", "USOILm", "..."],
  "watched": ["BTCUSD", "ETHUSD", "EURUSD"]
}
  • Use a name from symbols when placing orders; subscribe to a name to start it ticking on the WebSocket.
GET/v1/accounts/:id/symbol-specs

Per-symbol trading specs for the account: the volume constraints (min / max / step) for validating an order size before placing it, plus the base, profit (quote) and margin currency for each instrument. MT5 only; an MT4 account returns an empty list.

Path parameters
FieldTypeDescription
idreqstringaccountId.
200 OK
{
  "specs": [
    {
      "name": "EURUSD",
      "volumeMin": 0.01,
      "volumeMax": 200.0,
      "volumeStep": 0.01,
      "specSource": "broker",
      "baseCurrency": "EUR",
      "profitCurrency": "USD",
      "marginCurrency": "EUR"
    }
  ]
}
  • volumeStep is the lot increment — round an order size down to it before placing; volumeMin / volumeMax bound the size.
  • profitCurrency is the quote currency (the currency P&L accrues in). Use it — not the account currency — to denote an instrument.
  • specSource is "broker" (authoritative) or "derived" (a best-effort fallback when the broker did not supply the spec). Currency fields are absent when unknown.

Candles & history

Historical OHLC bars are included on every plan — no extra charge. The public endpoint GET /v1/public/candles (no API key required) returns bars at any of nine timeframes: M1, M5, M15, M30, H1, H4, D1, W1, MN1. Coarser timeframes reach further back — daily bars reach back years; a single request returns as much as fits in a few seconds.

The authed GET /v1/accounts/:id/candles takes either a look-back window (hours) or an exact date range (from + to, ISO-8601), and every response reports how much of the requested window was actually served via coverage and truncated.

GET/v1/accounts/:id/candles

Fetch historical OHLC bars from your connected broker, for any symbol the broker streams on this account. Two modes: a look-back window (hours) returns the most-recent N hours of bars, or a date range (from + to, ISO-8601) returns the exact [from, to] window. Coarser timeframes (H4, D1, W1, MN1) reach much further back — daily bars typically cover years of history. Every response reports how much of the requested window was actually served (coverage / truncated).

Path parameters
FieldTypeDescription
idreqstringaccountId.
Query parameters
FieldTypeDescription
symbolreqstringBroker-native symbol name, e.g. "BTCUSD". Discover names via GET /v1/accounts/:id/symbols.
hoursoptionalnumberLook-back mode: how many hours of data to return, counted backwards from now. Defaults to 24, capped at ~5 years. Ignored when from and to are supplied.
fromoptionalstring (ISO-8601)Date-range mode: start of the window, e.g. "2026-01-01T00:00:00Z". Pass BOTH from and to (an alternative to hours) to fetch the exact [from, to] window. Supplying only one is a 400 invalid_range.
tooptionalstring (ISO-8601)Date-range mode: end of the window. Required with from and must be after it. When both are present, hours is ignored.
timeframeoptional"M1"|"M5"|"M15"|"M30"|"H1"|"H4"|"D1"|"W1"|"MN1"Bar interval. Defaults to "M5". Coarser timeframes go back further for the same window.
200 OK
{
  "symbol": "BTCUSD",
  "hours": 17520,
  "timeframe": "D1",
  "candles": [
    { "timestamp": 1747699200, "open": 104200.10, "high": 107840.55, "low": 103520.00, "close": 106910.73, "bid": 106910.73 },
    { "timestamp": 1747785600, "open": 106910.73, "high": 108100.00, "low": 105480.20, "close": 107512.40, "bid": 107512.40 }
  ],
  "served": { "from": "2025-05-20T00:00:00.000Z", "to": "2025-05-21T00:00:00.000Z" },
  "count": 2,
  "coverage": "complete",
  "truncated": false,
  "stopReason": "floor"
}
  • Authed — needs your API key (same as the rest of the customer API). Works for any symbol your broker exposes on the connected account.
  • Two modes: pass hours for a look-back window, OR pass both from and to (ISO-8601) for an exact date range. When from and to are present, hours is ignored, and the response echoes from/to (the requested window) at the top level instead of hours. Supplying only one of from/to, an unparseable date, or from ≥ to returns 400 invalid_range with a message.
  • Each candle is { timestamp, open, high, low, close, bid, tickVolume, spread }. timestamp is the bar OPEN time in Unix seconds (UTC); bid mirrors close. tickVolume (tick count) and spread (price units) are present on recent bars; deep-history bars are bid-only and may omit them (null/absent) — don’t rely on a guaranteed volume.
  • Every response also reports completeness: served ({ from, to } actually returned in ISO-8601, or null when empty), count (number of candles), coverage ("complete" when the whole window was served, otherwise "floor"/"partial"), truncated (boolean — true when the whole requested window was NOT served; the authoritative completeness signal), and stopReason (why the walk stopped, e.g. "floor" = no deeper data exists, "deadline" = worth retrying, "unsupported", "error"). A note field is added when stopReason is "unsupported".
  • A range larger than the per-request cap (~5 years, or ~100,000 bars at the chosen timeframe) is rejected with 400 range_too_large ({ maxBars, estimatedBars, maxWindowDays }) — narrow the range or coarsen the timeframe.
  • Timeframes: M1, M5, M15, M30, H1, H4, D1, W1, MN1. Daily and coarser reach back years; intraday (M1–H4) covers recent months. One request returns as much history as fits in a few seconds. Deep look-backs are isolated onto a dedicated history connection — a big walk never disturbs your live tick stream.
  • If the broker returns no decodable bars for the symbol/range (e.g. an illiquid pair), the response is a 200 with an empty candles array (served null, truncated true) — never a 500.
GET/v1/public/candles

Unauthenticated read of the always-on demo feed — powers the sparklines and chart on tickerall.com. Limited to TickerAll’s demo symbol list and only callable from tickerall.com (origin-gated). For arbitrary broker symbols from your own code, use GET /v1/accounts/:id/candles above.

Query parameters
FieldTypeDescription
symbolreqstringOne of the demo feed’s symbols (e.g. BTCUSD, ETHUSD, EURUSD, GOLD).
hoursoptionalnumberHow many hours of data to return. Defaults to 24, capped at ~5 years.
timeframeoptional"M1"|"M5"|"M15"|"M30"|"H1"|"H4"|"D1"|"W1"|"MN1"Bar interval. Defaults to "M5". Coarser timeframes go back further for the same hours value.
200 OK
{
  "symbol": "BTCUSD",
  "hours": 17520,
  "timeframe": "D1",
  "candles": [
    { "timestamp": 1747699200, "open": 104200.10, "high": 107840.55, "low": 103520.00, "close": 106910.73, "bid": 106910.73 },
    { "timestamp": 1747785600, "open": 106910.73, "high": 108100.00, "low": 105480.20, "close": 107512.40, "bid": 107512.40 }
  ]
}
  • No API key needed, but origin-gated: this endpoint accepts requests from tickerall.com only and exists to drive the public demo widgets. For programmatic access from your own code use GET /v1/accounts/:id/candles instead — it works on any symbol your broker exposes.
  • Each candle is { timestamp, open, high, low, close, bid }. timestamp is the bar OPEN time in Unix seconds (UTC); bid mirrors close.
  • Only the demo feed’s symbol list is available here. For any other symbol, connect a broker account and call GET /v1/accounts/:id/candles instead.

Orders

Place market or pending orders, close positions (full or partial), and modify stop-loss / take-profit. All three require an Idempotency-Key header.

POST/v1/accounts/:id/ordersIdempotency-Key

Place a market order (fills immediately) or a pending limit/stop order (rests until price is hit).

Path parameters
FieldTypeDescription
idreqstringaccountId.
Request body (JSON)
FieldTypeDescription
typereq"market" | "limit" | "stop"The base order type — market (fills now) or limit / stop (rests until price is hit). Do NOT pass MetaTrader-style combined names like "BUY_STOP" here: those are only ever returned by GET /orders. On input, split the intent into type + side — e.g. a buy-stop is type:"stop" + side:"BUY".
symbolreqstringBroker-native symbol, e.g. "BTCUSD".
sidereq"BUY" | "SELL"Trade direction — uppercase BUY or SELL. Combined with type it expresses the order, e.g. type:"limit" + side:"SELL" is a sell-limit.
volumereqnumberLots, e.g. 0.10. Must be positive.
priceoptionalnumberTrigger price. Required for limit and stop; ignored for market.
stopLossoptionalnumberStop-loss price. Omit for none.
takeProfitoptionalnumberTake-profit price. Omit for none.
commentoptionalstring (≤ 31 chars)Optional strategy tag stored on the order.
201 Created
{
  "ticket": 4072808150,
  "symbol": "BTCUSD",
  "side": "BUY",
  "type": "market",
  "volume": 0.10,
  "price": null,
  "stopLoss": 71000,
  "takeProfit": 84000,
  "comment": "my-strategy",
  "status": "open",
  "timestamp": "2026-05-22T17:55:03.000Z"
}
  • Requires an Idempotency-Key header (see Conventions). Re-sending the same key returns the original response without placing a second order.
  • Pending orders are expressed as two separate fields, not one combined name: a buy-stop is type:"stop" + side:"BUY"; a sell-limit is type:"limit" + side:"SELL". The write API does NOT accept MetaTrader-style combined names (BUY_STOP, SELL_LIMIT, …) — passing type:"BUY_STOP" is a 400 VALIDATION_ERROR. GET /v1/accounts/:id/orders reports that combined name in its own type field for readability, but that is a read-only convenience: do not echo it back here — use its orderType (LIMIT/STOP) lowercased as type, plus side.
  • status is "open" for market orders and "pending" for limit/stop orders.
  • A broker rejection (bad volume, market closed, stop-level too tight, insufficient margin) comes back as 422 BROKER_REJECTED with the broker’s reason in message.
GET/v1/accounts/:id/orders

List the account’s working pending orders — LIMIT and STOP orders resting until their trigger price is hit. A market order is never pending: it becomes an open position immediately (see GET /v1/accounts/:id/positions). Returns an empty list when nothing is resting.

Path parameters
FieldTypeDescription
idreqstringaccountId.
200 OK
{
  "orders": [
    {
      "ticket": "4072809988",
      "symbol": "BTCUSD",
      "type": "BUY_LIMIT",
      "side": "BUY",
      "orderType": "LIMIT",
      "volume": 0.10,
      "price": 68000,
      "limitPrice": null,
      "stopLoss": 66000,
      "takeProfit": 72000,
      "setTime": "2026-08-14T09:12:44.000Z",
      "expirationTime": null
    }
  ]
}
  • Working (pending) orders only. When a pending order triggers it leaves this list and becomes an open position — find it under GET /v1/accounts/:id/positions.
  • type is one of BUY_LIMIT, SELL_LIMIT, BUY_STOP, SELL_STOP, BUY_STOP_LIMIT, SELL_STOP_LIMIT; orderType collapses that to LIMIT / STOP / STOP_LIMIT and side to BUY / SELL. ticket is a string; price is the trigger (activation) level; limitPrice is set only on STOP_LIMIT variants; expirationTime is null for good-till-cancelled.
  • This combined type (e.g. BUY_STOP) is READ-ONLY. To place or modify an order, use the split form — type (market/limit/stop) + side (BUY/SELL) — from POST /v1/accounts/:id/orders; the write API does not accept BUY_STOP-style names.
  • For live updates instead of polling, subscribe to the orders channel over the WebSocket (see the WebSocket section) — it pushes the full pending-order list on subscribe and on every change.
  • Optional ?waitMs=<0–10000> adds a settle window for a just-warmed connection’s first pending snapshot; omit for an immediate read.
  • Also reachable at the alias GET /v1/accounts/:id/orders/pending.
DELETE/v1/accounts/:id/orders/:ticketIdempotency-Key

Cancel a resting pending order (LIMIT or STOP) by its ticket.

Path parameters
FieldTypeDescription
idreqstringaccountId.
ticketreqnumberTicket of the pending order to cancel (from GET /v1/accounts/:id/orders).
200 OK
{
  "ticket": 4072809988,
  "symbol": "BTCUSD",
  "side": "BUY",
  "cancelled": true,
  "timestamp": "2026-08-14T09:12:44.000Z"
}
  • Requires an Idempotency-Key header.
  • ticket is the pending order’s ticket from GET /v1/accounts/:id/orders — not a position. If the order has already triggered it is now an open position; close it with DELETE /v1/accounts/:id/positions/:ticket instead.
  • If the ticket is not a resting pending order on this account you get 404 TICKET_NOT_FOUND.
  • Pending-order management is an MT5 feature; on an account that does not support it the call returns 400.
PATCH/v1/accounts/:id/orders/:ticketIdempotency-Key

Modify a resting pending order’s trigger price, stop-loss or take-profit. Any field you omit is preserved at its current value.

Path parameters
FieldTypeDescription
idreqstringaccountId.
ticketreqnumberTicket of the pending order to modify (from GET /v1/accounts/:id/orders).
Request body (JSON)
FieldTypeDescription
priceoptionalnumberNew trigger (activation) price. Omit to keep the current trigger.
stopLossoptionalnumberNew stop-loss. Omit to keep the current SL.
takeProfitoptionalnumberNew take-profit. Omit to keep the current TP.
200 OK
{
  "ticket": 4072809988,
  "symbol": "BTCUSD",
  "side": "BUY",
  "price": 66000,
  "stopLoss": 64000,
  "takeProfit": 72000,
  "timestamp": "2026-08-14T09:12:44.000Z"
}
  • Requires an Idempotency-Key header.
  • Provide at least one of price, stopLoss or takeProfit — an empty body is a 400. Omitted fields keep their current value.
  • If the ticket is not a resting pending order on this account you get 404 TICKET_NOT_FOUND.
DELETE/v1/accounts/:id/positions/:ticketIdempotency-Key

Close an open position. Omit volume for a full close, or pass a smaller volume for a partial close.

Path parameters
FieldTypeDescription
idreqstringaccountId.
ticketreqnumberTicket of the position to close (from the order response or GET /v1/accounts/:id).
Request body (JSON)
FieldTypeDescription
volumeoptionalnumberPartial-close volume in lots. If omitted, the whole position is closed.
200 OK
{
  "ticket": 4072808150,
  "symbol": "BTCUSD",
  "side": "BUY",
  "volume": 0.10,
  "closed": true,
  "timestamp": "2026-05-22T18:10:44.000Z"
}
  • Requires an Idempotency-Key header.
  • If the ticket is not an open position on this account you get 404 TICKET_NOT_FOUND.
PATCH/v1/accounts/:id/positions/:ticketIdempotency-Key

Modify the stop-loss and/or take-profit of an open position. Provide at least one of stopLoss / takeProfit.

Path parameters
FieldTypeDescription
idreqstringaccountId.
ticketreqnumberTicket of the position to modify.
Request body (JSON)
FieldTypeDescription
stopLossoptionalnumberNew stop-loss price. Omit to leave unchanged.
takeProfitoptionalnumberNew take-profit price. Omit to leave unchanged.
200 OK
{
  "ticket": 4072808150,
  "symbol": "BTCUSD",
  "side": "BUY",
  "volume": 0.10,
  "stopLoss": 72000,
  "takeProfit": 85000,
  "timestamp": "2026-05-22T18:12:09.000Z"
}
  • Requires an Idempotency-Key header.
  • You must supply at least one of stopLoss or takeProfit; sending neither is a VALIDATION_ERROR.
  • Some brokers enforce a minimum stop distance (stop level). Too-tight values come back as 422 BROKER_REJECTED.

Trade history

Your account’s closed-trade history — executed trades paired into round-trips (entry + exit) with realised P/L, the equivalent of MT5’s history_deals_get. Returns the recent window your broker provides on connect plus anything closed live during the session; filter by symbol and close-time range.

GET/v1/accounts/:id/history

Closed-trade history for the account — executed trades paired into round-trips (entry + exit), the equivalent of MT5’s history_deals_get. Returns the recent window your broker provides on connect plus any trades closed live during the session. Filter by symbol and close-time range.

Path parameters
FieldTypeDescription
idreqstringaccountId.
Query parameters
FieldTypeDescription
symboloptionalstringNarrow to one broker-native symbol, e.g. "ETHUSD". Omit for all symbols.
fromoptionalISO-8601 | epoch secondsOnly trades closed at/after this time.
tooptionalISO-8601 | epoch secondsOnly trades closed at/before this time.
limitoptionalnumberMax rows returned, newest-first. Defaults to 500, capped at 5000.
waitMsoptionalnumberHow long to wait (ms) for history to populate on a just-connected account. Defaults to 4000; pass 0 to skip the wait on a warm connection.
200 OK
{
  "trades": [
    {
      "ticket": "4072808150",
      "symbol": "ETHUSD",
      "side": "BUY",
      "volume": 0.10,
      "openPrice": 2500.50,
      "closePrice": 2510.25,
      "openTime": "2026-05-20T10:00:00.000Z",
      "closeTime": "2026-05-20T12:30:00.000Z",
      "profit": 0.98,
      "swap": 0,
      "commission": 0,
      "stopLoss": 0,
      "takeProfit": 0,
      "closeTicket": "4072808151",
      "complete": true
    }
  ],
  "count": 1,
  "limit": 500
}
  • Returns the recent window your broker pushes on connect (typically the last few weeks) plus trades closed live during the current session. from/to filter those rows — they do not fetch further back than the broker’s window.
  • Each row is a round-trip: ticket is the open/position ticket; closeTicket is the closing deal (may be null for a trade closed live this session). profit is realised P/L in the account currency.
  • complete=true is a confirmed round-trip with trustworthy P/L. complete=false marks an incomplete/unmatched row, where profit is reported as null rather than a misleading 0.
  • swap and commission are reported as 0 (not carried in this data set).
  • A cheap read that never disturbs your live tick stream. On a connection that has cooled you get 409 BROKER_ACCOUNT_NOT_HOT — POST /v1/sessions to reconnect.

Bulk operations

Execute one action across many of your accounts in a single request — place, close, modify, and cancel over a whole set of accounts, or read live state for your entire roster at once. Every bulk call reports each account’s outcome separately: a mix of successes and failures still returns 200, with a per-account results array and a summary tally, so a partial success is never ambiguous.

Bulk operations require a Pro or Enterprise plan; on the Free and Trader plans they return 403. The write calls take the same Idempotency-Key header as their single-account counterparts.

POST/v1/bulk/ordersIdempotency-Key

Place an order across many of your accounts in one request — one call fans out to every account you name, and each account’s outcome is reported separately. Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
ordersreqobject[]The orders to place — 1 to 50, one object per target: { accountId, type?, symbol, side, volume, price?, stopLoss?, takeProfit?, comment? }. accountId is the account to trade; type defaults to "market" ("limit"/"stop" need a price for a pending order); symbol, side and volume are required; stopLoss / takeProfit / comment are optional. Each entry mirrors the single-account POST /v1/accounts/:id/orders body.
200 OK
{
  "results": [
    { "accountId": "acc_8Kd3...", "status": "filled", "ticket": 4072808150, "price": 77512.73, "symbol": "BTCUSD" },
    { "accountId": "acc_9Lm4...", "status": "failed", "symbol": "BTCUSD", "code": "BROKER_REJECTED", "reason": "Not enough money" }
  ],
  "summary": { "total": 2, "filled": 1, "failed": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Requires an Idempotency-Key header (see Conventions). Re-sending the same key replays the original response without placing any order a second time.
  • Partial success — a mix of filled and failed accounts still returns 200. Read each account’s outcome in results: status is "filled" (with its ticket and fill price) or "failed" (with a code and human-readable reason). summary tallies total / filled / failed.
  • Demo accounts only for now — live-account bulk placement is coming soon. A live account included in the batch comes back failed rather than placing.
POST/v1/bulk/positions/closeIdempotency-Key

Close positions across many accounts in one request — either an explicit list of positions, or a per-account intent that flattens each account (optionally narrowed by its own broker-native symbol or side). Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
itemsoptionalobject[]Explicit mode: the exact positions to close, one object each: { accountId, ticket, volume? }. Omit volume for a full close, or pass a smaller volume for a partial close. Use this OR the intent fields below — not both.
targetsoptionalobject[]Intent mode: a per-account list, one object each: { accountId, symbol?, side? }. Every open position on that account is closed unless narrowed by its own symbol and/or side. Each target carries its own broker-native symbol, so a mixed-broker roster (Exness EURUSDm + XM EURUSD) works in one call. Use this OR items.
200 OK
{
  "results": [
    { "accountId": "acc_8Kd3...", "ticket": 4072808150, "status": "ok", "symbol": "BTCUSD", "side": "BUY", "volume": 0.10, "closed": true },
    { "accountId": "acc_9Lm4...", "ticket": 4072809002, "status": "failed", "symbol": "BTCUSD", "side": "SELL", "volume": 0.20, "closed": false, "code": "TICKET_NOT_FOUND", "reason": "Position not open" }
  ],
  "summary": { "total": 2, "ok": 1, "failed": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Requires an Idempotency-Key header. Re-sending the same key replays the original response without closing anything twice.
  • Two modes: pass items for an explicit per-position list, OR targets for a per-account intent (each { accountId, symbol?, side? }, with its own broker-native symbol). Supplying neither is a 400.
  • Partial success — each position’s outcome is in results: status "ok" (closed true) or "failed" (with a code and reason). summary tallies total / ok / failed.
POST/v1/bulk/positions/modifyIdempotency-Key

Modify the stop-loss and/or take-profit on positions across many accounts in one request. Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
itemsreqobject[]The positions to modify, one object each: { accountId, ticket, stopLoss?, takeProfit? }. Provide at least one of stopLoss / takeProfit per item; an omitted field keeps its current value.
200 OK
{
  "results": [
    { "accountId": "acc_8Kd3...", "ticket": 4072808150, "status": "ok", "symbol": "BTCUSD", "side": "BUY", "modified": true },
    { "accountId": "acc_9Lm4...", "ticket": 4072809002, "status": "failed", "symbol": "BTCUSD", "side": "SELL", "modified": false, "code": "BROKER_REJECTED", "reason": "Invalid stops" }
  ],
  "summary": { "total": 2, "ok": 1, "failed": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Requires an Idempotency-Key header.
  • Each item must carry at least one of stopLoss / takeProfit; an omitted field is preserved at its current value.
  • Partial success — per-position outcome in results: status "ok" (modified true) or "failed" (with a code and reason). summary tallies total / ok / failed.
POST/v1/bulk/orders/cancelIdempotency-Key

Cancel resting pending orders (LIMIT / STOP) across many accounts in one request — an explicit list, or a per-account intent that cancels the pending orders on each account (optionally narrowed by its own broker-native symbol). Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
itemsoptionalobject[]Explicit mode: the pending orders to cancel, one object each: { accountId, ticket }. Use this OR the intent fields below.
targetsoptionalobject[]Intent mode: a per-account list, one object each: { accountId, symbol? }. Cancels every resting pending order on that account, narrowed by its own broker-native symbol. Use this OR items.
200 OK
{
  "results": [
    { "accountId": "acc_8Kd3...", "ticket": 4072809988, "status": "ok", "cancelled": true },
    { "accountId": "acc_9Lm4...", "ticket": 4072809991, "status": "failed", "cancelled": false, "code": "TICKET_NOT_FOUND", "reason": "Not a resting pending order" }
  ],
  "summary": { "total": 2, "ok": 1, "failed": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Requires an Idempotency-Key header.
  • Two modes: items for an explicit list, OR targets for a per-account intent (each { accountId, symbol? }, with its own broker-native symbol). Supplying neither is a 400.
  • Partial success — per-order outcome in results: status "ok" (cancelled true) or "failed" (with a code and reason). summary tallies total / ok / failed.
  • Pending-order management is an MT5 feature; an entry on an account that does not support it comes back failed.
POST/v1/bulk/orders/modifyIdempotency-Key

Modify resting pending orders (trigger price, stop-loss, take-profit) across many accounts in one request. Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
itemsreqobject[]The pending orders to modify, one object each: { accountId, ticket, price?, stopLoss?, takeProfit? }. Provide at least one of price / stopLoss / takeProfit per item; an omitted field keeps its current value.
200 OK
{
  "results": [
    { "accountId": "acc_8Kd3...", "ticket": 4072809988, "status": "ok", "modified": true },
    { "accountId": "acc_9Lm4...", "ticket": 4072809991, "status": "failed", "modified": false, "code": "TICKET_NOT_FOUND", "reason": "Not a resting pending order" }
  ],
  "summary": { "total": 2, "ok": 1, "failed": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Requires an Idempotency-Key header.
  • Each item must carry at least one of price / stopLoss / takeProfit; an omitted field is preserved at its current value.
  • Partial success — per-order outcome in results: status "ok" (modified true) or "failed" (with a code and reason). summary tallies total / ok / failed.
GET/v1/bulk/accounts

Read live state for many accounts in one request — connection status, account financials and open positions for your whole roster (or a subset) in a single call. Requires a Pro or Enterprise plan.

Query parameters
FieldTypeDescription
idsoptionalstringComma-separated accountIds to read, e.g. "acc_8Kd3...,acc_9Lm4...". Omit to read every account on your key.
includeoptionalstringComma-separated list of what to include per account: "account", "positions". Defaults to both — e.g. include=account to skip positions and get a smaller response.
200 OK
{
  "accounts": [
    {
      "id": "acc_8Kd3...",
      "broker": "mt5",
      "server": "Exness-MT5Trial14",
      "accountNumber": "****5678",
      "externalRef": null,
      "isDemo": true,
      "hot": true,
      "poolId": "pool_3",
      "terminalType": "MOBILE",
      "alwaysHot": false,
      "lastHotAt": "2026-08-29T09:30:01.000Z",
      "createdAt": "2026-08-20T09:11:55.000Z",
      "status": "online",
      "account": { "balance": 9871.42, "currency": "USD", "equity": 9863.10, "margin": 142.50, "freeMargin": 9720.60, "marginLevel": 6921.5, "leverage": 500 },
      "positions": [
        { "ticket": 4072808150, "symbol": "BTCUSD", "side": "BUY", "volume": 0.10, "entryPrice": 77512.73, "currentPrice": 77640.10, "profit": 12.74 }
      ]
    },
    {
      "id": "acc_9Lm4...",
      "broker": "mt5",
      "server": "ICMarketsSC-Demo",
      "accountNumber": "****3311",
      "externalRef": null,
      "isDemo": true,
      "hot": false,
      "poolId": null,
      "terminalType": "WEB",
      "alwaysHot": false,
      "lastHotAt": "2026-08-29T08:05:44.000Z",
      "createdAt": "2026-08-21T14:02:10.000Z",
      "status": "offline"
    }
  ],
  "notFound": [],
  "summary": { "total": 2, "online": 1, "offline": 1 }
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403.
  • Not idempotent and takes no body — pass ids and include as query-string parameters.
  • One round-trip for your whole roster. Each account’s status is "online" (its account and positions blocks are present, per include) or "offline" (the connection has cooled — POST /v1/sessions to re-warm it; the account/positions blocks are omitted).
  • include controls the per-account payload: "account" adds the financials block, "positions" adds open positions; both are included by default. Drop one to make the response smaller.
  • Any ids you pass that are not on your key come back in notFound. summary tallies total / online / offline.

Copy Trading

Mirror one master account’s trades to many follower accounts — each scaled, symbol-mapped, and risk-clamped to its own size. Create a set, tune each follower, arm it, and the moment the master trades (through TickerAll) the followers follow. All accounts are your own (self-copy).

Copy Trading requires a Pro or Enterprise plan; on the Free and Trader plans these calls return 403 (COPY_REQUIRES_PRO). Sizing, lot clamps, exposure caps, symbol allow/block lists, reverse copy, a slippage guard, and per-broker symbol overrides are all per-follower. Read a set’s /stats and /log for a full picture of what mirrored.

Once a set is armed, any trade on the master mirrors to its followers automatically — whether it was placed through this API, the dashboard, a Telegram/Discord command, a webhook, or a TradingView alert. Point a TradingView strategy (or any signal source) at your master account and the whole set follows.

POST/v1/copy/sets

Create a copy set — one master account whose trades are mirrored to your follower accounts, each scaled and risk-clamped to its own size. All accounts are your own. Requires a Pro or Enterprise plan.

Request body (JSON)
FieldTypeDescription
namereqstringA label for the set.
masterAccountIdreqstringThe account whose trades are copied. Must be one of your own accounts (and never also a follower).
failurePolicyoptionalstringWhat to do when a follower copy fails: "retry" (a few backoff attempts, the default) or "skip".
webhookUrloptionalstringOptional. A public https:// URL that receives an HMAC-signed POST for every mirror outcome (see "Copy-event delivery" below).
webhookSecretoptionalstringOptional HMAC-SHA256 signing key (16+ chars) for the X-Tickerall-Signature header. Write-only — never returned.
followersoptionalobject[]Optional followers to attach now, one object each: { followerAccountId, ...config }. Per-follower settings, all optional: sizingMethod ("proportional" — scale by the follower÷master equity ratio, the default | "multiplier" | "fixed" | "risk_percent") and sizingValue (the multiplier factor, fixed lots, or risk %); minLot / maxLot (clamp + snap the copied volume to the follower broker’s lot step); maxOpenTrades / maxExposureLots (caps); symbolAllow / symbolBlock (string arrays of follower symbols); dailyLossStop (auto-pause on loss); reverse (inverse copy — sell when the master buys); maxSlippagePips (skip if the follower price moved too far from the master fill); minMasterLot (ignore the master’s tiny trades); copyDelayMs; symbolOverrides (a { "MASTERSYMBOL": "followerSymbol" } map for cross-broker names the auto-normalizer can’t resolve).
201 Created
{
  "id": "cset_7Hb2...",
  "ownerId": "usr_9Kd3...",
  "name": "My desk",
  "masterAccountId": "acc_master",
  "enabled": false,
  "failurePolicy": "retry",
  "webhookUrl": null,
  "hasWebhookSecret": false,
  "createdAt": "2026-08-29T12:00:00.000Z",
  "updatedAt": "2026-08-29T12:00:00.000Z",
  "followers": [
    { "id": "cf_1", "followerAccountId": "acc_1", "sizingMethod": "proportional", "reverse": false, "enabled": true }
  ]
}
  • Requires a Pro or Enterprise plan — on the Free and Trader plans this call returns 403 (COPY_REQUIRES_PRO).
  • Self-copy only — the master and every follower must be your own accounts. A follower cannot also be the master.
  • A new set is created paused (enabled false). Arm it with PATCH /v1/copy/sets/:setId { "enabled": true } once you’re happy with the followers.
  • While live copying is being rolled out, mirrored trades run on demo followers; managing sets and reading stats works on all accounts.
GET/v1/copy/sets

List your copy sets, each with a follower count. Requires a Pro or Enterprise plan.

200 OK
{
  "sets": [
    { "id": "cset_7Hb2...", "name": "My desk", "masterAccountId": "acc_master", "enabled": true, "failurePolicy": "retry", "_count": { "followers": 3 }, "createdAt": "2026-08-29T12:00:00.000Z", "updatedAt": "2026-08-29T12:00:00.000Z" }
  ]
}
  • Requires a Pro or Enterprise plan.
GET/v1/copy/sets/:setId

Get one copy set with its full follower list + config. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
200 OK
{
  "id": "cset_7Hb2...",
  "name": "My desk",
  "masterAccountId": "acc_master",
  "enabled": true,
  "failurePolicy": "retry",
  "followers": [
    { "id": "cf_1", "followerAccountId": "acc_1", "sizingMethod": "multiplier", "sizingValue": 0.5, "maxLot": 1, "reverse": false, "enabled": true }
  ]
}
  • Requires a Pro or Enterprise plan.
  • Returns 404 if the set is not yours.
PATCH/v1/copy/sets/:setId

Update a set — rename, change the failure policy, or arm / pause it. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
Request body (JSON)
FieldTypeDescription
nameoptionalstringNew label.
failurePolicyoptionalstring"retry" or "skip".
enabledoptionalbooleanArm (true) — start mirroring — or pause (false). Pausing leaves existing follower positions untouched.
webhookUrloptionalstring | nullSet the copy-event webhook (public https:// URL), or null to clear it.
webhookSecretoptionalstring | nullSet the HMAC signing key (16+ chars), or null to clear it. Write-only.
200 OK
{ "id": "cset_7Hb2...", "name": "My desk", "enabled": true, "failurePolicy": "retry", "followers": [ ... ] }
  • Requires a Pro or Enterprise plan.
  • Provide at least one field. Arming is just enabled: true.
DELETE/v1/copy/sets/:setId

Delete a copy set (and its followers, position map, and log). Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
204 No Content
204 No Content — empty body.
  • Requires a Pro or Enterprise plan.
  • Open follower positions are NOT closed — deleting a set only stops future mirroring.
POST/v1/copy/sets/:setId/followers

Add a follower to a set. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
Request body (JSON)
FieldTypeDescription
followerAccountIdreqstringThe account to mirror to (one of your own; not the master, not already a follower).
...configoptionalobjectPer-follower settings, all optional: sizingMethod ("proportional" — scale by the follower÷master equity ratio, the default | "multiplier" | "fixed" | "risk_percent") and sizingValue (the multiplier factor, fixed lots, or risk %); minLot / maxLot (clamp + snap the copied volume to the follower broker’s lot step); maxOpenTrades / maxExposureLots (caps); symbolAllow / symbolBlock (string arrays of follower symbols); dailyLossStop (auto-pause on loss); reverse (inverse copy — sell when the master buys); maxSlippagePips (skip if the follower price moved too far from the master fill); minMasterLot (ignore the master’s tiny trades); copyDelayMs; symbolOverrides (a { "MASTERSYMBOL": "followerSymbol" } map for cross-broker names the auto-normalizer can’t resolve).
201 Created
{ "id": "cf_4", "copySetId": "cset_7Hb2...", "followerAccountId": "acc_4", "sizingMethod": "proportional", "reverse": true, "maxSlippagePips": 3, "enabled": true }
  • Requires a Pro or Enterprise plan.
  • The follower must be your own account, not the master, and not already in the set.
PATCH/v1/copy/sets/:setId/followers/:followerId

Update a follower’s config — only the fields you send change. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
followerIdreqstringThe follower id (cf_...), from the set’s followers list.
Request body (JSON)
FieldTypeDescription
...configoptionalobjectAny subset of Per-follower settings, all optional: sizingMethod ("proportional" — scale by the follower÷master equity ratio, the default | "multiplier" | "fixed" | "risk_percent") and sizingValue (the multiplier factor, fixed lots, or risk %); minLot / maxLot (clamp + snap the copied volume to the follower broker’s lot step); maxOpenTrades / maxExposureLots (caps); symbolAllow / symbolBlock (string arrays of follower symbols); dailyLossStop (auto-pause on loss); reverse (inverse copy — sell when the master buys); maxSlippagePips (skip if the follower price moved too far from the master fill); minMasterLot (ignore the master’s tiny trades); copyDelayMs; symbolOverrides (a { "MASTERSYMBOL": "followerSymbol" } map for cross-broker names the auto-normalizer can’t resolve). Send a field as null to clear it.
200 OK
{ "id": "cf_4", "copySetId": "cset_7Hb2...", "followerAccountId": "acc_4", "sizingMethod": "fixed", "sizingValue": 0.02, "maxLot": 1 }
  • Requires a Pro or Enterprise plan.
DELETE/v1/copy/sets/:setId/followers/:followerId

Remove a follower from a set. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
followerIdreqstringThe follower id (cf_...).
204 No Content
204 No Content — empty body.
  • Requires a Pro or Enterprise plan.
  • Open positions the follower already holds are NOT closed.
GET/v1/copy/sets/:setId/stats

Dashboard stats for a set — totals, replication rate, and per-follower rollups. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
200 OK
{
  "set": { "id": "cset_7Hb2...", "name": "My desk", "enabled": true, "masterAccountId": "acc_master", "failurePolicy": "retry", "followerCount": 3 },
  "totals": { "ok": 128, "skipped": 4, "failed": 2, "replicationRate": 0.9846 },
  "byAction": { "open": 66, "close": 60, "modify": 8 },
  "followers": [
    { "followerAccountId": "acc_1", "enabled": true, "sizingMethod": "proportional", "ok": 44, "skipped": 1, "failed": 0, "openPositions": 2, "avgLatencyMs": 138 }
  ]
}
  • Requires a Pro or Enterprise plan.
  • Derived from the copy log: totals tally ok / skipped / failed; replicationRate is ok ÷ (ok + failed). Per follower: outcome counts, current open copied positions, and average fill latency.
GET/v1/copy/sets/:setId/log

The copy log for a set — every mirrored action and its outcome, newest first. Requires a Pro or Enterprise plan.

Path parameters
FieldTypeDescription
setIdreqstringThe copy set id.
Query parameters
FieldTypeDescription
limitoptionalnumberQuery param. Page size, 1–200 (default 50).
beforeoptionalstringQuery param. An ISO timestamp — return entries older than this. Use the response’s nextBefore to page.
200 OK
{
  "entries": [
    { "id": "clg_9", "followerAccountId": "acc_1", "action": "open", "masterTicket": "4072808150", "followerTicket": "5510022931", "symbol": "EURUSDm", "mappedSymbol": "EURUSD", "volume": 0.01, "result": "ok", "latencyMs": 132, "createdAt": "2026-08-29T12:34:56.000Z" },
    { "id": "clg_8", "followerAccountId": "acc_2", "action": "open", "symbol": "XAUUSDm", "volume": null, "result": "skipped", "reason": "XAUUSD is on the block list", "createdAt": "2026-08-29T12:34:56.000Z" }
  ],
  "nextBefore": "2026-08-29T12:34:56.000Z"
}
  • Requires a Pro or Enterprise plan.
  • Newest first. limit and before are query-string parameters; page by passing the previous response’s nextBefore back as before (null means the end).
  • result is "ok", "skipped" (with a reason — e.g. filtered by a rule), or "failed" (with a reason). action is open / close / partial_close / modify / pending_place / pending_cancel / pending_modify.
Copy-event delivery (webhooks)

Set a webhookUrl on a copy set (with an optional webhookSecret) to receive a JSON POST for every mirror outcome — ok, skipped, or failed. It’s the same stream the set’s /log records, delivered as it happens. Delivery is best-effort and never blocks or delays a trade.

POST body — one copy event
{
  "event": "copy.open.ok",          // copy.<action>.<result>
  "setId": "cset_7Hb2...",
  "setName": "My desk",
  "action": "open",                  // open | close | partial_close | modify | pending_cancel | pending_modify
  "result": "ok",                    // ok | skipped | failed
  "followerAccountId": "acc_1",
  "symbol": "EURUSD",
  "mappedSymbol": "EURUSDm",         // the follower broker's symbol
  "volume": 0.25,
  "masterTicket": "123456",
  "followerTicket": "998877",
  "reason": null,                    // why, when skipped/failed
  "latencyMs": 140,
  "ts": "2026-08-29T12:00:00.000Z"
}

The event is copy.<action>.<result> (e.g. copy.close.failed) so you can route on it. When a webhookSecret is set, each request carries an X-Tickerall-Signature: sha256=<hex> header — the HMAC-SHA256 of the raw request body, keyed by your secret. Verify it before trusting the payload:

import { createHmac, timingSafeEqual } from 'crypto'

function verify(rawBody, signatureHeader, secret) {
  const expected = 'sha256=' + createHmac('sha256', secret).update(rawBody).digest('hex')
  const a = Buffer.from(signatureHeader), b = Buffer.from(expected)
  return a.length === b.length && timingSafeEqual(a, b)
}

Live chat alerts, no bot setup

Discord / Telegram

Discord and Telegram channels both expose an incoming webhook URL. Point webhookUrl at one to stream mirror events straight into a chat — a zero-code way to get live copy alerts on your phone.

Webhooks & TradingView

Turn a POSTed JSON payload into a trade — from a TradingView alert, or any source that can send an HTTP POST (a script, Zapier, your own backend). Each connected account has its own incoming webhook URL, and the URL identifies the account — so no login or credentials ever go in the payload. Create one under Dashboard → TradingView, where you also get per-symbol aliases, an optional shared secret, and a dry-run test.

Webhook URL — per account, shown in the dashboard
/api/webhooks/tv/<token>     # TradingView — paste into the alert's "Webhook URL"
/api/hook/<token>            # any other source — same token, same account

Put the JSON in the TradingView alert message (or the POST body). Only action plus the fields that action needs are required:

  • actionbuy · sell · close · close_all · modify
  • symbol — auto-resolved to the broker’s name (BTCUSDBTCUSDm), case-insensitive
  • type — add "limit" / "stop" + price for a pending order
  • optional — volume (a partial close), sl, tp, ticket (target one position), comment
Payloads
# Market buy
{"action":"buy","symbol":"XAUUSD","volume":0.10}

# Pending order with SL/TP
{"action":"sell","type":"limit","symbol":"XAUUSD","volume":0.10,"price":2400,"sl":2410,"tp":2380}

# Partial close — take a chunk off (e.g. TP1/TP2/TP3; send one per level)
{"action":"close","symbol":"XAUUSD","volume":0.03}

# Close the whole position on a symbol
{"action":"close","symbol":"XAUUSD"}

# Modify stop / take-profit — breakeven = sl at entry; trail = re-send with the new sl
{"action":"modify","symbol":"XAUUSD","sl":2345.0,"tp":2380.0}

# Close every open position on the account
{"action":"close_all"}

Each webhook has an optional required secret and per-symbol aliases in its settings, plus a Test button that dry-runs a payload before you go live. Live trading follows the same plan rules as the rest of the API — see Plans & limits.

Want a full walkthrough with Pine Script templates and copy-paste alerts? See the companion guide: github.com/TickerAll/tradingview-mt5-mt4.

WebSocket — realtime data

Open a single long-lived WebSocket to wss://api.tickerall.com/v1/stream for live data. Authenticate with the same bearer token (header on the upgrade, or ?token=… in the URL). After connecting, send a subscribe message listing the channels you want.

There are four channel kinds — ticks (per-symbol price updates), positions (open/update/close events), orders (your resting pending LIMIT/STOP orders — the full book, re-sent whole on every change), and account (balance / equity snapshots). All are scoped by accountId.

Client → server: subscribe
send
{
  "type": "subscribe",
  "channels": [
    { "kind": "ticks", "accountId": "acc_8Kd3...", "symbols": ["BTCUSD", "ETHUSD"] },
    { "kind": "positions", "accountId": "acc_8Kd3..." },
    { "kind": "orders", "accountId": "acc_8Kd3..." },
    { "kind": "account", "accountId": "acc_8Kd3..." }
  ],
  "correlationId": "sub-1"
}

The server replies with a subscribed frame echoing which channels were accepted and which were rejected (with a code — see below). Unsubscribe with the same channel shape and "type": "unsubscribe". Send { "type": "ping" } to get a pong and keep the connection alive.

Server → client: pushes
receive
// price tick
{ "type": "tick", "accountId": "acc_8Kd3...", "symbol": "BTCUSD",
  "bid": 77512.73, "ask": 77514.10, "timestamp": "2026-05-22T18:01:22.317Z" }

// position lifecycle (event: "opened" | "updated" | "closed")
{ "type": "position_update", "accountId": "acc_8Kd3...", "event": "opened",
  "position": { "ticket": 4072808150, "symbol": "BTCUSD", "side": "BUY",
                "volume": 0.10, "entryPrice": 77512.73, "profit": 0 } }

// pending-order book — the FULL current list, re-sent whole on every change
{ "type": "order_update", "accountId": "acc_8Kd3...",
  "orders": [ { "ticket": "4072809988", "symbol": "BTCUSD", "type": "BUY_LIMIT",
                "side": "BUY", "orderType": "LIMIT", "volume": 0.10, "price": 68000,
                "stopLoss": 66000, "takeProfit": 72000 } ] }

// account snapshot
{ "type": "account_update", "accountId": "acc_8Kd3...",
  "snapshot": { "balance": 9871.42, "equity": 9863.10, "margin": 142.50 } }

// subscribe acknowledgement
{ "type": "subscribed", "channels": [ ... ], "rejected": [], "correlationId": "sub-1" }
Subscribe rejection codes
CodeMeaning
INVALID_MESSAGEThe frame was not valid JSON or did not match the message schema.
RATE_LIMITYou sent messages too fast. Slow down and retry.
NOT_FOUNDSubscribe rejected: no account with that accountId.
FORBIDDENSubscribe rejected: that account is not yours.
BROKER_ACCOUNT_NOT_HOTSubscribe rejected: connection cooled. Call POST /v1/sessions to reconnect.
CHANNEL_LIMITSubscribe rejected: too many channels on this connection.

Protocol-level problems arrive as an error frame: { "type": "error", "code": "RATE_LIMIT", "message": "Slow down." }. The connection sends WebSocket ping frames as a heartbeat — reply with pong (most client libraries do this automatically) or you will be disconnected.

Errors

Every REST error uses the same envelope and a meaningful HTTP status. error is a stable machine code; message is human-readable. Validation failures add a details array naming the offending fields.

error envelope
{
  "error": "BROKER_REJECTED",
  "message": "Broker rejected the order: invalid volume",
  "details": [ /* present only on VALIDATION_ERROR */ ]
}
Common error codes
CodeHTTPMeaning
UNAUTHORIZED401Missing, malformed, or invalid Authorization header / API key.
VALIDATION_ERROR400The request body or params failed validation. A details array lists the offending fields.
BROKER_AUTH_FAILED401The broker rejected the login — wrong account number, password, or server. Returned by POST /v1/sessions and POST /v1/accounts/:id/reconnect. Fix the detail and retry.
BROKER_UNREACHABLE503Could not reach the broker (network/endpoint down). Retry shortly. (A wrong password no longer maps here — see BROKER_AUTH_FAILED.)
BROKER_ACCOUNT_NOT_HOT409The connection cooled. Call POST /v1/sessions with credentials to reconnect.
BROKER_REJECTED422The broker refused the order/close/modify. The reason is in message (e.g. bad volume, market closed, stop level).
TICKET_NOT_FOUND404The position ticket is not open on this account.
BROKER_ACCOUNT_NOT_FOUND404No broker account with that id belongs to your key.
BROKER_ACCOUNT_ALREADY_LINKED409That broker account is already linked to another TickerAll customer.
FREE_TIER_LIVE_REJECTED403The Free tier only supports demo accounts. Upgrade to Pro to connect a real-money account.
DEMO_ACCOUNT_RESERVED403That broker account is reserved by TickerAll for the public demo and cannot be attached.
TIER_ACCOUNT_CAP_REACHED403You hit your plan’s broker-account cap. Upgrade, or contact us for Enterprise.
INTERNAL_ERROR500Unexpected server error. Safe to retry idempotent calls.

Plans & limits

Tiers, account caps, always-hot, and prices live on the pricing page — the single source of truth for what each plan includes and costs. This section covers only what plans mean for the API: what’s metered, and the responses that gate each tier.

What’s metered

Reads — balances, positions, ticks, candles, history — are uncapped on every plan. Demo orders are always free and unlimited. What a paid plan buys is the number of live broker accounts you can connect and trade — a per-account cap, not a per-call quota.

Pro & Enterprise features

Bulk operations (/v1/bulk/*) and Copy Trading (/v1/copy/*) require a Pro or Enterprise plan. Choosing a non-mobile connection origin (the web or desktop terminal) is a Pro feature too.

The plan-gating responses you’ll see from the API:

  • FREE_TIER_LIVE_REJECTED — a real-money login on the Free plan (Free accepts demo accounts only).
  • 403 TIER_ACCOUNT_CAP_REACHED — you’ve hit your plan’s live-account cap; demo accounts don’t count toward it.
  • 403 COPY_REQUIRES_PRO — a Copy Trading call on a plan below Pro.
  • Bulk endpoints return 403 on the Free and Trader plans — they need Pro or Enterprise.

For the actual tiers, prices, caps, and overage, see the pricing page. Need more than Pro covers? Talk to us about Enterprise.

Ready to ship?

Grab an API key and make your first POST /v1/sessions in five minutes.

Sign up — free
API Docs · Ticker All!