Claim gumball cNFT

Refused (400) for royalty-bearing items — those must finalize via settle-cnft-sale (settle-first ordering).

A compressed NFT may need an address lookup table before its transaction fits the 1232-byte packet. When no usable one exists, the response carries a setupTx alongside tx: sign and confirm it first, then broadcast tx.

Authorization

ApiKeyAuth

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

payer*string

gumballMachine*string

seller*string

buyer*string

mint*string

index*integer

Formatuint32

targetPriorityFeeLamports?integer

Priority fee per transaction, in lamports: an endpoint that returns several transactions (an edition buy of several copies, a chunked collection edit) applies it to each one. By default this is a cap: mallow prices the transaction from current network conditions and pays at most this much, or at most 50,000 lamports when omitted. With exactPriorityFee: true it is the fee to pay instead. Either way the fee never goes below a floor: 15,000 lamports, or 15,000 micro-lamports per compute unit when the transaction's compute limit is above 1,000,000 units (up to 21,000 lamports at the 1,400,000-unit maximum). A value under the floor pays the floor. The fee is rounded up to a whole micro-lamport per compute unit, so it can land a lamport or two above this value. Ignored, along with exactPriorityFee, when mallow pays the fee (Cream and Reward payments, subsidized mints and edits) and on an edition buy that swaps currency in the same transaction: those use the network estimate capped at 50,000 lamports.

Formatuint64

exactPriorityFee?boolean

Pay targetPriorityFeeLamports exactly rather than using it as a cap. Defaults to false. When true, mallow skips its network fee estimate and sets the compute-unit price so the transaction pays the target (subject to the same floor). Has no effect without targetPriorityFeeLamports, and is ignored wherever that field is.

Response Body

`application/json`

curl -X POST "https://example.com/v2/tx/gumball/claim-cnft" \  -H "Content-Type: application/json" \  -d '{    "payer": "string",    "gumballMachine": "string",    "seller": "string",    "buyer": "string",    "mint": "string",    "index": 0  }'

{  "result": {    "tx": "string",    "setupTx": "string"  }}

Authorization

Request Body

Response Body

200application/json

400application/json

401application/json

429application/json

500application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`