receiptOrders

Order management, status tracking, and lifecycle actions

Order details

get
/api/v1/partner/orders/{order_id}

Get the current status, amounts, and full timeline for a specific order. The next_action field indicates what the partner should do next (e.g., authorize_crypto_transfer). The allowed_actions array lists all API actions available for the current status (e.g., ["authorize-crypto-transfer", "cancel"]). Each entry corresponds to a POST /api/v1/partner/orders/{order_id}/{action} endpoint.

Status mapping: Internal trade statuses are mapped to simplified partner-facing statuses. See the PartnerOrderStatus enum for all possible values.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Path parameters
order_idstring · uuidRequired

Order UUID returned by the initiate endpoint

Example: b2c3d4e5-f6a7-8901-bcde-f12345678901
Responses
chevron-right
200

Order retrieved successfully

application/json
get
/api/v1/partner/orders/{order_id}

Get transfer authorization parameters

get
/api/v1/partner/orders/{order_id}/transfer-authorization-parameters

Returns pre-filled parameters required to build and sign the EIP-712 forward request. Use this endpoint first, then sign locally and send the signature to /api/v1/partner/orders/{order_id}/authorize-crypto-transfer.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Path parameters
order_idstring · uuidRequired

Order UUID

Responses
chevron-right
200

Transfer authorization parameters returned

application/json
get
/api/v1/partner/orders/{order_id}/transfer-authorization-parameters

Authorize crypto transfer

post
/api/v1/partner/orders/{order_id}/authorize-crypto-transfer

Submit signed EIP-712 forward_request to authorize transfer of order crypto to escrow.

Security note: Your private key is never sent to the API. The SDK uses it locally to construct and sign the EIP-712 ForwardRequest on your machine. Only the resulting signature and the unsigned forward_request fields are submitted. You can verify this by reading the SDK source code.

Recommended: use SDK helper files (only 4 arguments needed):

  • Python: https://github.com/Unigox/sdk_python/blob/main/partner_authorize_crypto_transfer_sdk.py

  • JavaScript: https://github.com/Unigox/sdk_javascript/blob/main/partner_authorize_crypto_transfer_sdk.js

The SDK automatically fetches all required parameters (chain, token, forwarder, escrow address, RPC URL) from the transfer-authorization-parameters endpoint.

SDK helper options:

  • End-to-end one call: authorize_crypto_transfer(...) / authorizeCryptoTransfer(...)

  • Build unsigned request only: build_forward_request(...) / buildForwardRequest(...)

  • Sign existing request only: sign_forward_request(...) / signForwardRequest(...)

  • Build full request body {forward_request, signature}: build_authorize_crypto_transfer_payload(...) / buildAuthorizeCryptoTransferPayload(...)

Manual implementation: call GET /transfer-authorization-parameters first, then build the EIP-712 typed data and sign with your partner wallet private key locally.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Path parameters
order_idstring · uuidRequired

Order UUID

Example: b2c3d4e5-f6a7-8901-bcde-f12345678901
Body
forward_requestobjectRequired

Signed EIP-712 ForwardRequest payload

signaturestringRequired

Hex-encoded signature from partner wallet

Responses
chevron-right
200

Crypto authorization accepted

No content

post
/api/v1/partner/orders/{order_id}/authorize-crypto-transfer

No content

Confirm fiat received

post
/api/v1/partner/orders/{order_id}/confirm-fiat-received

Confirm that fiat payment has been received by the user for an off-ramp order. This triggers the crypto release from escrow to the buyer.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Path parameters
order_idstring · uuidRequired

Order UUID

Example: b2c3d4e5-f6a7-8901-bcde-f12345678901
Responses
chevron-right
200

Fiat receipt confirmed successfully

No content

post
/api/v1/partner/orders/{order_id}/confirm-fiat-received

No content

Cancel order

post
/api/v1/partner/orders/{order_id}/cancel

Cancel an order if cancellation is allowed at the current status. Check allowed_actions on the order response — cancel is available when cancellation is permitted.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Path parameters
order_idstring · uuidRequired

Order UUID

Example: b2c3d4e5-f6a7-8901-bcde-f12345678901
Responses
chevron-right
200

Order cancelled successfully

No content

post
/api/v1/partner/orders/{order_id}/cancel

No content

List orders

get
/api/v1/partner/orders

Get a paginated list of orders with optional filtering by status. Each order includes allowed_actions indicating which API actions are available.

Authorizations
X-API-KeystringRequired

Partner API key for authentication. Required for all partner account endpoints.

Query parameters
statusstring · enumOptional

Filter by partner order status

Example: completedPossible values:
pageintegerOptional

Page number (default 1)

Default: 1Example: 1
limitinteger · max: 100Optional

Results per page (default 20, max 100)

Default: 20Example: 20
Responses
chevron-right
200

Orders retrieved successfully

application/json
get
/api/v1/partner/orders

Last updated