Skip to main content
GET
Reconcile a submitted redemption preparation
Use the original preparationId after an interrupted checkout. Once the order is available, use its requestId to read the shipping details.

Request

Builder key and wallet access token

Response

On HTTP 200, check the checkout status. For failed or submitting, look up the original preparation before another payment.

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

preparationId
string<uuid>
required

Response

Success

requestId
string
required
status
enum<string>
required
Available options:
prepared,
submitting,
succeeded,
failed
transactionHash
string