Cancel Tensor listing

Builds a transaction cancelling seller's Tensor (TCMP) listing of asset and returning the asset to their wallet.

The listing is read fresh from chain and seller must be its owner; anyone else is rejected with a 400, as is an asset with no Tensor listing. The listing account's rent goes back to whoever paid it. Token Metadata NFTs, programmable NFTs, Core assets, Token-2022 NFTs and Bubblegum v1 compressed NFTs are supported. Mallow charges no fee.

Authorization

ApiKeyAuth

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Cancel the caller's own Tensor listing and return the escrowed asset.

seller*string

The Tensor listing's owner wallet (base58). It signs, pays, and receives the asset back.

asset*string

The listed asset as mallow addresses it (base58): a Token Metadata or Token-2022 mint, a Core asset, or a compressed NFT's asset id.

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.

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/tensor/delist" \  -H "Content-Type: application/json" \  -d '{    "seller": "string",    "asset": "string"  }'

{  "result": {    "tx": "string"  }}

Cancel Tensor listing

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`