RULE CHANGE
Trading with the API
take_market and take_limit order types now support attached TP/SL; PUT endpoint expanded to manage exits on these orders.
What this means
take_market and take_limit order types changed from supporting only opening conditional orders to supporting opening conditional orders and attached TP/SL. The PUT /v1/orders/{order_id}/attached-exits endpoint now applies to resting limit, stop_market, stop_limit, take_market, or take_limit entries, expanded from the previous set of resting limit, stop_market, or stop_limit entries. PATCH and DELETE endpoints remain unchanged.
▸ View exact changes
The change in place, line by line
Before Oct 29, 2026
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
| stop_market | trigger_price | attached TP/SL, or reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
−
| type | Required price fields | Important options |
|---|---|---|
| take_market | trigger_price | opening conditional order |
| take_limit | trigger_price, limit_price | opening conditional order |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
Some instruments are listed on more than one venue. GET /v1/markets returns
each instrument's default venue; GET /v1/markets?venues=all also returns its
alternate venues, with default_venue: false. Trade an alternate venue by
sending its market_id, the same choice the trade page's venue switcher
offers. An account holds an instrument on one venue at a time: an order that
would open on a second venue while a position is open on another is rejected
with venue_conflict. Close the existing position first. TWAP and scaled
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
− a resting limit, stop_market, or stop_limit entry. Send null to remove
− a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.
After Oct 31, 2026
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
| stop_market | trigger_price | attached TP/SL, or reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
+
| type | Required price fields | Important options |
|---|---|---|
| take_market | trigger_price | opening conditional order, attached TP/SL |
| take_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
Some instruments are listed on more than one venue. GET /v1/markets returns
each instrument's default venue; GET /v1/markets?venues=all also returns its
alternate venues, with default_venue: false. Trade an alternate venue by
sending its market_id, the same choice the trade page's venue switcher
offers. An account holds an instrument on one venue at a time: an order that
would open on a second venue while a position is open on another is rejected
with venue_conflict. Close the existing position first. TWAP and scaled
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
+ a resting limit, stop_market, stop_limit, take_market, or take_limit
+ entry. Send null to remove a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
| stop_market | trigger_price | attached TP/SL, or reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
−
| type | Required price fields | Important options |
|---|---|---|
| take_market | trigger_price | opening conditional order |
| take_limit | trigger_price, limit_price | opening conditional order |
+
| type | Required price fields | Important options |
|---|---|---|
| take_market | trigger_price | opening conditional order, attached TP/SL |
| take_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
Some instruments are listed on more than one venue. GET /v1/markets returns
each instrument's default venue; GET /v1/markets?venues=all also returns its
alternate venues, with default_venue: false. Trade an alternate venue by
sending its market_id, the same choice the trade page's venue switcher
offers. An account holds an instrument on one venue at a time: an order that
would open on a second venue while a position is open on another is rejected
with venue_conflict. Close the existing position first. TWAP and scaled
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
− a resting limit, stop_market, or stop_limit entry. Send null to remove
− a leg.
+ a resting limit, stop_market, stop_limit, take_market, or take_limit
+ entry. Send null to remove a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.