Skip to main content
POST
Refresh tracking for an authorized redemption order
Refresh a specific order with its original builder key and a wallet access token for its owner. Display tracking details when the courier provides them.

Request

Builder key and wallet access token

Response

Error codes

Match the HTTP status and response text to a row below. For guidance on codes shared across endpoints, see Error meanings and recovery.

Authorizations

x-builder-api-key
string
header
required

Your approved builder API key. Keep it on your backend. Gacha and marketplace writes also require wallet action signatures. Redeem also needs a wallet access token, a Bearer token the API issues after the wallet signs a sign-in message.

Authorization
string
header
required

Wallet access token: Bearer authentication for Redeem

Path Parameters

requestId
string
required
Pattern: ^0x[\da-fA-F]{64}$

Response

Success

requestId
string
required

32 bytes encoded as 0x followed by 64 hexadecimal digits.

status
string
required
tokenStatuses
object
required
address
object
required
recipient
object
required
courierName
string
required
estimatedDeliveryDaysMin
number | null
required
estimatedDeliveryDaysMax
number | null
required
fees
object
required
trackingNumber
string | null
required
trackingUrl
string | null
required
shipmentStatus
string | null
required
trackingLastSyncedAt
string | null
required
createdAt
string<date-time>
required
updatedAt
string<date-time> | null
required
collectibles
object[]
required