RULE CHANGE
API capabilities
Account events API now includes price alert fires; price alerts capability added separately.
What this means
Account events WebSocket stream expanded to include price alert fires in addition to order, fill, position, and balance changes. New price alerts capability allows creating, listing, moving, re-arming, and deleting chart price alerts with read scope sufficient; alerts notify but never trade. Trading policy and copy trading capabilities unchanged.
▸ View exact changes
The change in place, line by line
Before Oct 31, 2026
Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders.
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Entry protection | Attached TP/SL on market and non-reduce-only limit, stop, and take entries. |
| Order lifecycle | Read working orders and paginated history; modify supported working orders, cancel, and update attached exits. |
| Position lifecycle | Read open and closed positions; close fully or partially using market, limit, or external conditional orders. |
| Protective exits | Batch TP/SL placement, modification, cancellation, and OCO pairing, including price-capped exits. |
| Margin | Supply leverage and margin mode when placing orders; add or remove extra isolated margin by setting its target total. |
| Execution strategies | Create, inspect, and cancel TWAP, VWAP, and scaled ladders. Use the documented status filters when listing strategy parents. |
| Account-wide actions | Resumable cancel-all ordinary orders and close-all positions. Strategy parents require separate cancellation. |
| Reconciliation | Order IDs, caller-assigned IDs for ordinary and close orders, paginated fills, and partial-fill lineage. |
| Copy trading | List, save, and disable copy-trading groups whose members the credential can access, and acknowledge a completed copy stop. |
| Trading policy | Read an account's effective rules, trading limits, restrictions, payout and copy locks, and trading halts. |
−
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Account events | A WebSocket stream of order, fill, position, and balance changes across the key's accounts. |
See Trading with the API for behavior and examples and the
REST reference for request and response fields.
Features that require the website
The public REST contract has no endpoints for these website capabilities:
- Signup and onboarding, challenge purchases, identity verification, agreements,
payout requests, and billing or purchase-history management.
- API-key creation and management or sandbox-account creation and reset.
- Saved trading preferences, watchlists, and notifications.
- Journal notes and tags, performance dashboards, and account equity-history charts.
Existing copy-trading configurations still apply when an API request trades a
lead account. Inspect those groups through the API or on the website before
running an automated strategy. The API lists only groups whose lead and every
After Nov 2, 2026
Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders.
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Entry protection | Attached TP/SL on market and non-reduce-only limit, stop, and take entries. |
| Order lifecycle | Read working orders and paginated history; modify supported working orders, cancel, and update attached exits. |
| Position lifecycle | Read open and closed positions; close fully or partially using market, limit, or external conditional orders. |
| Protective exits | Batch TP/SL placement, modification, cancellation, and OCO pairing, including price-capped exits. |
| Margin | Supply leverage and margin mode when placing orders; add or remove extra isolated margin by setting its target total. |
| Execution strategies | Create, inspect, and cancel TWAP, VWAP, and scaled ladders. Use the documented status filters when listing strategy parents. |
| Account-wide actions | Resumable cancel-all ordinary orders and close-all positions. Strategy parents require separate cancellation. |
| Reconciliation | Order IDs, caller-assigned IDs for ordinary and close orders, paginated fills, and partial-fill lineage. |
| Copy trading | List, save, and disable copy-trading groups whose members the credential can access, and acknowledge a completed copy stop. |
| Trading policy | Read an account's effective rules, trading limits, restrictions, payout and copy locks, and trading halts. |
+
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Price alerts | Create, list, move, re-arm, and delete chart price alerts. Read scope is enough; alerts notify and never trade. |
| Account events | A WebSocket stream of order, fill, position, and balance changes across the key's accounts, plus price alert fires. |
See Trading with the API for behavior and examples and the
REST reference for request and response fields.
Features that require the website
The public REST contract has no endpoints for these website capabilities:
- Signup and onboarding, challenge purchases, identity verification, agreements,
payout requests, and billing or purchase-history management.
- API-key creation and management or sandbox-account creation and reset.
- Saved trading preferences, watchlists, and notifications.
- Journal notes and tags, performance dashboards, and account equity-history charts.
Existing copy-trading configurations still apply when an API request trades a
lead account. Inspect those groups through the API or on the website before
running an automated strategy. The API lists only groups whose lead and every
Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders.
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Entry protection | Attached TP/SL on market and non-reduce-only limit, stop, and take entries. |
| Order lifecycle | Read working orders and paginated history; modify supported working orders, cancel, and update attached exits. |
| Position lifecycle | Read open and closed positions; close fully or partially using market, limit, or external conditional orders. |
| Protective exits | Batch TP/SL placement, modification, cancellation, and OCO pairing, including price-capped exits. |
| Margin | Supply leverage and margin mode when placing orders; add or remove extra isolated margin by setting its target total. |
| Execution strategies | Create, inspect, and cancel TWAP, VWAP, and scaled ladders. Use the documented status filters when listing strategy parents. |
| Account-wide actions | Resumable cancel-all ordinary orders and close-all positions. Strategy parents require separate cancellation. |
| Reconciliation | Order IDs, caller-assigned IDs for ordinary and close orders, paginated fills, and partial-fill lineage. |
| Copy trading | List, save, and disable copy-trading groups whose members the credential can access, and acknowledge a completed copy stop. |
| Trading policy | Read an account's effective rules, trading limits, restrictions, payout and copy locks, and trading halts. |
−
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Account events | A WebSocket stream of order, fill, position, and balance changes across the key's accounts. |
+
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
|---|---|
| Price alerts | Create, list, move, re-arm, and delete chart price alerts. Read scope is enough; alerts notify and never trade. |
| Account events | A WebSocket stream of order, fill, position, and balance changes across the key's accounts, plus price alert fires. |
See Trading with the API for behavior and examples and the
REST reference for request and response fields.
Features that require the website
The public REST contract has no endpoints for these website capabilities:
- Signup and onboarding, challenge purchases, identity verification, agreements,
payout requests, and billing or purchase-history management.
- API-key creation and management or sandbox-account creation and reset.
- Saved trading preferences, watchlists, and notifications.
- Journal notes and tags, performance dashboards, and account equity-history charts.
Existing copy-trading configurations still apply when an API request trades a
lead account. Inspect those groups through the API or on the website before
running an automated strategy. The API lists only groups whose lead and every