The Orders endpoints cover the full order lifecycle on Pacifica: placing market and limit orders, attaching take-profit and stop-loss targets, editing and cancelling orders individually or in bulk, submitting batch operations, and querying open orders and history. All mutating endpoints (POST) require a cryptographic signature.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/pacifica-fi/docs-migrate/llms.txt
Use this file to discover all available pages before exploring further.
All POST endpoints on this page require request signing. See the Authentication guide for details on how to generate a valid signature.
POST /api/v1/orders/create_market — Create Market Order
Submits a new market order with optional take-profit and stop-loss levels.This endpoint requires a signed request. Set the
type header field to "create_market_order" when generating your signature. See Authentication.To protect liquidity providers from adverse selection, all market orders are subject to a ~200 ms delay before execution.User’s wallet address.
Cryptographic signature over the request payload.
Current timestamp in milliseconds.
Trading pair symbol, e.g.
BTC.Order amount in the asset’s base unit, e.g.
"0.1".Order side:
"bid" (long) or "ask" (short).Maximum slippage tolerance as a percentage, e.g.
"0.5" means 0.5%.Whether the order is reduce-only.
Client-defined UUID order ID, e.g.
"f47ac10b-58cc-4372-a567-0e02b2c3d479".Optional take-profit stop order configuration.
Optional stop-loss order configuration (same fields as
take_profit).Agent wallet address.
Signature expiry in milliseconds.
Builder program code (3–16 alphanumeric characters).
Exchange-assigned ID for the newly created order.
POST /api/v1/orders/create — Create Limit Order
Submits a new limit order with optional take-profit and stop-loss levels.This endpoint requires a signed request. Set the
type header field to "create_order". See Authentication.GTC and IOC limit orders are subject to a ~200 ms taker speedbump to protect liquidity providers.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
Limit price, e.g.
"50000".Order amount in the asset’s base unit.
"bid" or "ask".Time-in-force:
GTC (Good Till Cancelled), IOC (Immediate or Cancel), ALO (Add Liquidity Only / Post-Only), or TOB (Top of Book).Whether the order is reduce-only.
Client-defined UUID order ID.
Optional take-profit configuration (see Create Market Order for field details).
Optional stop-loss configuration (see Create Market Order for field details).
Agent wallet address.
Signature expiry in milliseconds.
Builder program code (3–16 alphanumeric characters).
POST /api/v1/orders/stop/create — Create Stop Order
Creates a standalone stop or stop-limit order attached to an existing or future position.This endpoint requires a signed request. Set the
type header field to "create_stop_order". See Authentication.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
"bid" or "ask".Whether the order is reduce-only.
Stop order configuration.
Agent wallet address.
Signature expiry in milliseconds.
Builder program code (3–16 alphanumeric characters).
POST /api/v1/positions/tpsl — Create Position TP/SL
Sets or replaces take-profit and stop-loss levels on an existing open position.This endpoint requires a signed request. Set the
type header field to "set_position_tpsl". See Authentication.At least one of take_profit or stop_loss must be provided.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
Position side:
"bid" (long) or "ask" (short).Take-profit configuration (required if
stop_loss is absent).Stop-loss configuration (required if
take_profit is absent).Agent wallet address.
Signature expiry in milliseconds.
Builder program code (3–16 alphanumeric characters).
POST /api/v1/orders/cancel — Cancel Order
Cancels a single open order by its exchange-assigned order ID or client order ID.This endpoint requires a signed request. Set the
type header field to "cancel_order". See Authentication.Cancel requests are not affected by any speedbumps.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
Exchange-assigned order ID. Required if
client_order_id is not provided.Client-defined UUID order ID. Required if
order_id is not provided.Agent wallet address.
Signature expiry in milliseconds.
POST /api/v1/orders/cancel_all — Cancel All Orders
Cancels all open orders, either across all symbols or for a specific symbol.This endpoint requires a signed request. Set the
type header field to "cancel_all_orders". See Authentication.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
true to cancel orders across all symbols.true to skip reduce-only orders during the bulk cancel.Specific symbol to cancel orders for. Required when
all_symbols is false.Agent wallet address.
Signature expiry in milliseconds.
Number of orders successfully cancelled.
POST /api/v1/orders/stop/cancel — Cancel Stop Order
Cancels a stop order by its exchange-assigned ID or client order ID.This endpoint requires a signed request. Set the
type header field to "cancel_stop_order". See Authentication.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
Exchange-assigned order ID. Required if
client_order_id is not provided.Client-defined UUID. Required if
order_id is not provided.Agent wallet address.
Signature expiry in milliseconds.
POST /api/v1/orders/edit — Edit Order
Modifies the price and/or size of an existing limit order. Editing cancels the original order and creates a new one with TIFALO (Post-Only). The new order retains the same side and reduce-only status.
This endpoint requires a signed request. Set the
type header field to "edit_order". See Authentication.Edit order is not subject to the taker speedbump. Provide either order_id or client_order_id, not both.User’s wallet address.
Cryptographic signature.
Current timestamp in milliseconds.
Trading pair symbol.
New order price.
New order amount.
Exchange-assigned order ID. Required if
client_order_id is not provided.Client-defined UUID. Required if
order_id is not provided.Agent wallet address.
Signature expiry in milliseconds.
The new exchange-assigned order ID for the edited order.
POST /api/v1/orders/batch — Batch Order
Submits up to 10 order actions atomically in a single request. Actions are executed in the order they appear and are not interleaved with other users’ orders.Batch orders are not signed as a whole. Each individual action within the
actions array must carry its own signature, timestamp, and account fields — identical to the corresponding standalone endpoint.Speedbump behaviour: The batch is delayed ~200 ms if it contains any CreateMarket actions or Create actions with TIF GTC or IOC. Batches containing only ALO/TOB orders, cancels, or TP/SL operations are not delayed.Ordered list of action objects. Each action has a
type string and a data object.Per-action result objects in the same order as the request.
GET /api/v1/orders — Get Open Orders
Returns all currently open orders for a given account. RequestAccount address to filter orders.
Exchange-assigned order ID.
Client-defined UUID if provided at order creation.
Trading pair symbol.
"bid" or "ask".Order limit price.
Total order size in the asset’s base unit.
Amount filled so far.
Amount cancelled.
Stop trigger price attached to the order, if any.
One of
"limit", "market", "stop_limit", "stop_market", "take_profit_limit", "stop_loss_limit", "take_profit_market", "stop_loss_market".ID of the parent order this stop is attached to.
Whether the order is reduce-only.
Timestamp (ms) when the order was created.
Timestamp (ms) of the last order modification.
Exchange-wide sequential nonce for reliable event ordering.
GET /api/v1/orders/history — Get Order History
Returns a paginated summary of all historical orders for an account. RequestAccount address.
Maximum number of records to return. Defaults to
100.Pagination cursor. Omit to start from the most recent records.
Exchange-assigned order ID.
Client-defined UUID if provided.
Trading pair symbol.
"bid" or "ask".Submitted limit price.
Volume-weighted average price at which the order was filled.
Total order size in base units.
Amount filled.
One of
"open", "partially_filled", "filled", "cancelled", "rejected".Order type (see Open Orders for possible values).
Stop trigger price if applicable.
ID of the parent order this stop is attached to.
Whether the order is reduce-only.
Cancellation or rejection reason:
"cancel", "force_cancel", "expired", "post_only_rejected", "self_trade_prevented".Timestamp (ms) when the order was created.
Timestamp (ms) of the last modification.
Cursor for the next page.
true when additional pages exist.GET /api/v1/orders/history_by_id — Get Order History by ID
Returns the full event history for a single order, showing every state transition including creation, fills, adjustments, and cancellation. RequestExchange-assigned order ID.
Unique ID for this history event.
Exchange-assigned order ID.
Client-defined UUID if provided.
Trading pair symbol.
"bid" or "ask".Execution price for this event (limit price at creation, fill price at match, or limit price at cancellation).
Original order size.
Cumulative filled amount at the time of this event.
Amount cancelled at the time of this event.
Type of order lifecycle event. Possible values:
"make", "stop_created", "twap_created", "fulfill_market", "fulfill_limit", "adjust", "stop_parent_order_filled", "stop_triggered", "stop_upgrade", "twap_triggered", "cancel", "force_cancel", "expired", "post_only_rejected", "self_trade_prevented".Order type (see Open Orders for possible values).
One of
"open", "partially_filled", "filled", "cancelled", "rejected".Stop trigger price assigned to the order, if applicable.
ID of the parent order this stop is attached to, if applicable.
Whether the order is reduce-only.
Timestamp (ms) when this event was recorded.