Pulls and buybacks
Submit a buyback for polling
Each accepted submission creates a new request. Poll GET /v2/gacha/buyback/status with its requestId for the outcome.
POST
Submit a signed buyback and poll its requestId
- Sign. Have the seller sign
BuybackUserAuthorizationfor settlement IDs from the same pack. Submit the same body and builder key used by Settle a buyback. An ID from another pack can return HTTP404withEOA_PURCHASE_REJECTED. - Track. Save
requestIdfrom HTTP202. Check buyback status about once per second untilCOMPLETEDorFAILED. Each submission creates a separate request. - Handle a failure. A failed request carries the same error code as a direct settlement. For
OP_WALLET_BUSY, retry with the same signature. For other failures, refresh the offers and request a new signature.
Request
Builder key and wallet signature
Response
HTTP202 returns status: "PENDING", error: null and a new requestId. Use Get buyback status for settlement failures.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
Body
application/json
Response
Each accepted submission creates a new request. Poll GET /v2/gacha/buyback/status with its requestId for the outcome.