Create a QRC721 Token Collection Transaction

Prepare a QRC721 token collection transaction for signing

Transforms a transaction request ready to be signed and returns a request ID for executing. The supported transaction types are “Approve Asset Collect” and “Collect Asset”. The “Approve Asset Collect” transaction type will allow you to approve someone to subsequently make a transaction that takes the NFT from your address into their own. The “Collect Asset” transaction type will create the transaction to pull the approved NFT from an account into the receiving account. Successfully prepared transactions can then be executed using the /execution/transaction API.

SecurityOAuth2_Security_Scheme
Request
header Parameters
Authorization
required
string [ 0 .. 5010 ] characters ^Bearer [A-Za-z0-9\-_. ]{1,5010}$
Request Body schema: application/json
One of:
urgency
required
string [ 0 .. 30 ] characters ^[A-Za-z ]{1,30}

This value defines how fast a transaction is processed on a network. A faster processing requirement will result in higher fees. If the urgency field is not provided, the default setting is normal

Enum: "Normal" "Fast" "Urgent"
required
object (PaymentRequestDetailsSchema)

The payload request

required
object (Location)

Unique reference to the ledger on a particular ledger network (optionally accessed from a particular node)

type
required
string [ 0 .. 30 ] characters ^[A-Za-z ]{1,30}

The type of the transaction

Enum: "Payment" "Transfer" "Contract Invoke"
Responses
200

All good!

401

Unauthorised

500

Something went wrong on our side

post/v2/tokenise/preparation/transaction/qrc721/collect
Request samples
application/json

Prepare Approve collect for QRC721

{
  • "urgency": "normal",
  • "requestDetails": {
    },
  • "location": {
    },
  • "type": "Approve Asset Collect"
}
Response samples
application/json

Prepare Collect Response

{
  • "gatewayFee": {
    },
  • "requestId": "a7db0ee3-ed9c-409a-9b51-57075a570aa0",
  • "dltFee": {
    },
  • "nativeData": {
    }
}