Endpoint
Request Body
Use the
operationId from Update Leverage or
Update Isolated Margin. A leverage
selection returned as applied has no asynchronous operation to query.
Signing
UsebuildIsolatedOperationStatusTypedData with a connected Viem walletClient:
NotionalSignTransaction domain, version 1, the supplied chainId, and the
zero address as verifyingContract. The primary type is IsolatedOperationStatus, containing
user: address, operationId: bytes32, and timestamp: uint64.
This is a separate signing format from NotionalExchange actions. There is no exchange nonce.
The timestamp may be at most five minutes old or one minute in the future. Re-sign when polling
beyond that window; the operationId stays unchanged.
Response
- 200: Pending
- 200: Completed
- 200: Failed
operation is leverage_update or margin_update; direction appears only for margin updates.
completedAt is a Unix-millisecond observation time and appears only for terminal results. A
failed result additionally has error.code and error.details with a structured reason and phase.
Errors
400: malformed address, ID, timestamp, chain ID, or signature format.401: invalid, stale, future-dated, or unauthorized signature.404: no matching operation for this user, including settings-only leverage selections.503: the request history or operation status cannot currently be read reliably.
status: "failed" is still a successful HTTP 200 status lookup. Inspect its
body before updating the client.