Skip to main content
POST
Prepare a purchase and Permit2 typed data
Compare the returned chain, wallet, pack, price and quantity with the purchase the buyer reviewed before asking them to sign. See Gacha integration.Before submitting, check the wallet’s allowance for approval.spender on approval.token. If it is below approval.requiredAmount, approve that amount and wait for confirmation.

Request

Builder key required

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.

Body

application/json
buyerWalletAddress
string
required
packId
string<uuid>
required
quantity
integer
default:1
Required range: 1 <= x <= 10

Response

Success

chainId
integer
required
buyerWalletAddress
string
required

20-byte, 0x-prefixed wallet or contract address. Use lowercase or a valid checksum.

pack
object
required
permit2TypedData
object
required
unsignedPullPayload
object
required
approval
object
required