Skip to main content
GET
Get the status of one of this builder's pulls by confirmed funding transaction
Send the original buyer wallet and funding hash with the same builder key. A transaction from another builder returns HTTP 404.A result can arrive before the card reaches the wallet. See buybacks and delivery for custody, transfer confirmation and when a draw becomes public.

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.

Query Parameters

buyerWalletAddress
string
required
permitFundTxHash
string
required

Response

Success

permitFundTxHash
string
required

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

buyerWalletAddress
string
required

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

packId
string<uuid>
required
packName
string
required
status
enum<string>
required
Available options:
PENDING_RESOLUTION,
RESOLVED
numOfTokens
integer
required
pulledAt
string<date-time> | null
required
draws
object[]
required