Edit collection artworks

Builds the transaction(s) that add or remove members of the Core parent collection parentCollection, signed by authority.

Pass any combination of addAssets, removeAssets, addMasterEditions and removeMasterEditions — they are applied together.

Unlike the other builders this returns an array: { "result": { "txs": [{ "tx": "..." }] } }. Membership changes are batched to fit Solana's transaction size limit, so a large edit spans several transactions. Sign and broadcast every entry, in the order returned.

Authorization

ApiKeyAuth

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Adds and/or removes members of a Core parent collection. All four lists are applied together; pass any combination.

authority*string

Wallet performing the change (base58). Must hold update authority over the collection.

parentCollection*string

Address of the Core parent collection being modified (base58).

groupSigner?string

Keypair address co-signing the Core group operation, when the collection requires one.

addAssets?array<string>

Asset addresses to add to the collection (base58).

removeAssets?array<string>

Asset addresses to remove from the collection (base58).

addMasterEditions?array<string>

Master-edition addresses to add to the collection (base58).

removeMasterEditions?array<string>

Master-edition addresses to remove from the collection (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/nft/edit-collection-artworks" \  -H "Content-Type: application/json" \  -d '{    "authority": "string",    "parentCollection": "string"  }'

{  "result": {    "txs": [      {        "tx": "string"      }    ]  }}

Edit collection artworks

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`