Skip to main content
POST
Submit a prepared EOA redemption once
Completing redemption burns the selected NFTs. Submit the payment once. If the connection drops, look up the checkout with the original preparation ID. Reusing the ID returns its recorded state.A successful checkout starts the redemption order. Check the order for dispatch and tracking updates.

Request

Builder key, wallet access token and wallet signature

Response

HTTP 200 can carry status: "failed" without a reason code. For failed or submitting, look up the original preparationId 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

Body

application/json
preparationId
string<uuid>
required
signature
string
required
Pattern: ^0x(?:[a-fA-F0-9]{128}|[a-fA-F0-9]{130})$

Response

Success

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