API Reference — NFTs

All write operations use the v2 signed transaction API (client-side signing).

Read Endpoints

List Collections

GET /api/nft/collections

Get Collection

GET /api/nft/collection/:id

Get Collection Tokens

GET /api/nft/collection/:id/tokens

Get Token

GET /api/nft/token/:collection_id/:token_id

Get NFTs by Owner

GET /api/nft/owner/:pubkey

Matches the owner exactly as recorded — normally the owner's hex public key. Querying with a rouge1… address does not return NFTs owned by the public key.

Write Endpoints (v2 Signed)

All write endpoints accept a signed transaction body:

{
  "payload": { "type": "nft_mint", "..." },
  "signature": "...",
  "public_key": "..."
}

Create Collection

POST /api/v2/nft/collection/create

Payload fields: symbol, name, maxSupply, royaltyBps, royaltyRecipient, image, description Fee: 50 XRGE

royaltyBps — royalty in basis points (500 = 5%). From CONTRACT_NFT_ROYALTY activation it must be an integer 0–10000; anything else (above 100%, negative, fractional) returns 400 royaltyBps must be an integer between 0 and 10000.
royaltyRecipient — (optional) wallet that receives secondary-sale royalties. Defaults to the creator when omitted, and is fixed at creation. A wallet address or a deployed contract address (for example a royalty-splitter contract, which pays collaborators on-chain). ⚠️ The address is not validated: royalties sent to a mistyped address, or to a contract with no way to pay XRGE out, cannot be recovered.

Mint NFT

POST /api/v2/nft/mint

Payload fields: collectionId, name, metadataUri, attributes Fee: 5 XRGE

Batch Mint

POST /api/v2/nft/batch-mint

Payload fields: collectionId, names, uris, attributes (array, one entry per NFT) Fee: 5 XRGE per NFT

Note: the node reads per-NFT attributes only from attributes. @rougechain/sdk 1.11.0+ and the current site sign them there (batchMint({ ..., attributes }); the old batchAttributes option is a deprecated alias). SDK ≤ 1.10.0 sent a batchAttributes payload field, which the node ignores, so attributes passed through those versions were not stored — upgrade the SDK. When signing payloads yourself, use attributes.

Transfer NFT

POST /api/v2/nft/transfer

Payload fields: collectionId, tokenId, to, salePrice Fee: 1 XRGE

When salePrice > 0 and the collection has a royalty, the sender also pays salePrice × royaltyBps / 10000 XRGE to the collection's royaltyRecipient (on top of the fee). salePrice is self-declared — a transfer with no salePrice pays no royalty.

Burn NFT

POST /api/v2/nft/burn

Payload fields: collectionId, tokenId Fee: 0.1 XRGE

Lock/Unlock NFT

POST /api/v2/nft/lock

Payload fields: collectionId, tokenId, locked Fee: 0.1 XRGE

Freeze Collection

POST /api/v2/nft/freeze-collection

Payload fields: collectionId, frozen Fee: 0.1 XRGE

RougeChain Documentation