Skip to main content
POST
Build cancel-order payload
Lighter requires the wallet to be a registered account before any trade/withdraw action.If the EOA has never deposited on Lighter, this endpoint will fail. First-time setup is a two-step prerequisite:
  1. Deposit ≥ 5 USDC via /2/perp/payloads/deposit → Lighter creates an accountIndex on-chain once the bridge settles. (5 USDC is a Lighter requirement, not a Mobula limit.)
  2. Provision API key + auth token via /2/perp/payloads/create-account using that accountIndex.
Read the Build Create-Account Payload page for the full setup flow including how to discover the accountIndex after a deposit.
Builds the payload to cancel an unfilled order. For Gains, orderType distinguishes pending limit orders (order) from TP/SL legs (tp, sl) attached to an open trade.

Request Body

dex
string
required
gains or lighter.
chainId
string
required
Chain of the order.
orderIndex
string
required
Order index as a positive integer string (regex ^\d+$). Obtainable from /2/wallet/perp/orders.
marketId
string
Mobula market identifier. Required by Lighter.
orderType
string
Gains only. One of order, tp, sl. Omit for Lighter.

Authentication

Every /2/perp/payloads/<action> endpoint verifies the caller by requiring two extra fields in the request body alongside the action parameters:
timestamp
number
required
Unix timestamp in milliseconds. Must be within 30 seconds of server time. Older timestamps are rejected to prevent replay.
signature
string
required
Hex signature (EIP-191 personal_sign) of the message `${endpoint}-${timestamp}`, where endpoint is the path of this endpoint without the leading slash (e.g., for this page: api/2/perp/payloads/<this-action>). The recovered signer address becomes the user for the request. Single-use — replay returns 403 signature already used.

Authentication errors

Statusmessage
403timestamp expired — timestamp older than 30s
403signature already used — replay attempt
400zod validation failedtimestamp/signature shape invalid

Response envelope

Every /2/perp/payloads/<action> endpoint returns the same envelope shape. You pass these fields verbatim into POST /2/perp/execute-v2 to execute the action.
Top-level shape. Successful (2xx) responses return { data: { ... } }. A success: true flag is only present inside the body of execute-v2’s response, not on the payload-build endpoints. Parse defensively: read body.data, then check for the action-specific fields you need (e.g. data.payloadStr).
data
object

Endpoint-specific errors

Statusmessage
400cancel-order payload generation failed — order not found or DEX refusal

Full flow — cancel an order end-to-end

Single example covering both DEXes (Lighter offchain-api, Gains evm-tx). The flow branches on data.transport.

Body

application/json
timestamp
number
required
signature
string
required
dex
enum<string>
required
Available options:
gains,
lighter
chainId
string
required
orderIndex
string
required

Positive integer string (regex ^\d+$).

marketId
string

Required by Lighter.

orderType
enum<string>

Gains only. Omit for Lighter.

Available options:
order,
tp,
sl

Response

200 - application/json

Canonical payload envelope

success
boolean
required
data
object
required