Skip to main content
POST
Submit a signed bid acceptance
Use the response from prepare to accept a bid. Send its top-level tokenId and copy askData and bidOrderId from payload. Include the seller’s askSignature.On testnet, submit the top-level tokenId shown here. Until the mainnet release, send the prepared payload.collectibleId as top-level collectibleId on mainnet. Keep the signed order data exactly as prepared.

Request

Builder key and wallet signature

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
tokenId
string
required

Copy the top-level tokenId from preparation. It must have the same uint256 value as askData.tokenId. Keep it as a decimal string.

Pattern: ^\d+$
Example:

"9007199254740993"

askData
object
required

Copy payload.askData from the same preparation. Preserve the signed fields, including the deadline in whole Unix seconds.

askSignature
string
required
bidOrderId
string<uuid>
required

Response

Success

operation
enum<string>
required
Available options:
ask,
bid,
buy,
sell
orderId
string
required
status
enum<string>
required
Available options:
ACTIVE,
EXECUTED
executed
boolean
required
executionTxHash
string
matchedOrderId
string