Settle auction

Builds the transaction that closes out asset's ended auction, signed by authority.

Settling transfers the asset to the winning bidder and distributes proceeds — marketplace fee, royalties to the creators recorded on-chain, and the remainder to the seller. authority need not be the seller; anyone may settle an auction that has ended and has a winner, which lets a buyer claim without waiting on the seller.

Auctions with endTime set can only be settled once that time has passed, otherwise 400. An auction with no end time settles on demand once a bid exists.

If the auction ended with no bids, this instead builds the reclaim path returning the asset to the seller — and then only the seller may call it.

Authorization

ApiKeyAuth

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Closes out an ended auction: transfers the asset to the winning bidder and distributes proceeds. With no bids, it instead builds the reclaim path returning the asset to the seller.

authority*string

Wallet signing and paying for the settlement (base58). Need not be the seller — anyone may settle an ended auction that has a winner. When the auction ended with no bids, only the seller may call it.

asset*string

Mint address of the artwork under auction (base58).

targetPriorityFeeLamports?integer

Total priority fee to target for this transaction, in lamports. The builder derives the compute-unit price from it and the transaction's compute budget. Omit to let mallow pick a fee from current network conditions.

Formatuint64

blockhash?string

Recent blockhash to stamp onto the transaction, base58. Omit to let mallow supply one — mallow's is cached for up to 10 seconds, so two identical requests inside that window compile the same transaction, with the same signature once signed. Supply your own to control the expiry window, or when otherwise-identical requests must produce distinct transactions. Rejected with a 400 if it is not valid base58; a blockhash the cluster has already aged out builds fine and fails at send time.

Response Body

`application/json`

curl -X POST "https://example.com/v2/tx/auctions/settle" \  -H "Content-Type: application/json" \  -d '{    "authority": "string",    "asset": "string"  }'

{  "result": {    "tx": "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`