Skip to main content
GET
Check perp process status
Some actions submitted to /2/perp/execute-v2 are asynchronous — the most common case is deposit on Lighter, which must observe the underlying bridge/settlement before the user’s margin is usable. When the execute-v2 response includes a processId, poll this endpoint until the process reports a terminal status.

Query Parameters

processId
string
required
UUID returned by /2/perp/execute-v2 in data.processId.

Response

Unwrapped body. Unlike every other perp route ({ data: { ... } }), this endpoint returns the fields below at the top level — there is no data envelope. Parse defensively if your client assumes the wrapped shape.
processId
string
UUID of the tracked process.
status
string
Process status reported by the execution engine (e.g., pending, settled, failed). Terminal values depend on the action; clients should treat any non-pending value as final.
message
string
Human-readable status message.
errorMessage
string
Error detail, present only when the process failed.

Errors

Statusmessage
404Process not found or tracking disabled — unknown processId, or the instance has process tracking disabled

Query Parameters

processId
string
required

UUID returned by /2/perp/execute-v2 in data.processId.

Response

Process status

processId
string
required
status
string
required
message
string
errorMessage
string