Prepare A Non Fungible Token Transfer From Address
Using this endpoint customers can prepare a non-fungible token transfer from an address with private and public keys. The address doesn’t have to belong to a wallet. The response will include the transaction fee in Wei.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
Requirednetwork string
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "mordor" are test networks.
Query parameters
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.
Request body schema application/json
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user. -
Requireddata object
-
Requireditem object
-
Requiredcontract string
Represents the contract address of the token, which controls its logic. It is not the address that holds the tokens.
-
Optionalnonce string
Represents the sequential running number for an address, starting from 0 for the first transaction. E.g., if the nonce of a transaction is 10, it would be the 11th transaction sent from the sender's address.
-
Requiredrecipient string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.
-
Requiredsender string
Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sende
-
RequiredtokenId string
Represents the unique token identifier.
-
Requiredfee object
-
OptionalexactAmount string
Representation of the exact amount to be transfered.
-
Requiredpriority string
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast"
-
-
OptionaltransactionType string
Representation of the transaction type. For Ethereum-Classic and Binance Smart Chain there is no need to provide "transactionType" in the request.
-
-
Response schema
Content-Type: application/json
The resource has been successfully submitted.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.Example : yourExampleString -
Requireddata object
-
Requireditem object
-
Requiredrecipient string
Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.
Example : 0x5668213c59ab2612ecd948f98371d1d291098b5e -
Requiredsender string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.
Example : 0xc6d46aba0c6e2eb6358c4e24804158cc4d847922 -
RequiredtokenId string
Represents the unique token identifier.
Example : 14 -
RequiredblockchainSpecific object One Ofobject
-
OptionaldataHex string
0x0079006f00750072004100640064006900740069006f006e0061006c00440061007400610048006500720065
Example : 0x23b872dd000000000000000000000000c6d46aba0c6e2eb6358c4e24804158cc4d8479220000000000000000000000000902a667d6a3f287835e0a4593cae4167384abc6000000000000000000000000000000000000000000000000000000000000000e -
Optionalnonce string
Represents the sequential running number for an address, starting from 0 for the first transaction. E.g., if the nonce of a transaction is 10, it would be the 11th transaction sent from the sender's address.
Example : 1 -
RequiredsigHash string
Representation of the hash that should be signed
Example : 1b0ba4f497e39a74aa9a83afde0ec257c5c6e8547ea8187c319f0a242c2506f4 -
Requiredfee object
Defines the amount of the transaction fee.
-
RequiredgasLimit string
Represents the amount of gas used by this specific transaction alone.
Example : 552020 -
RequiredgasPrice string
Represents the price offered to the miner to purchase this amount of gas.
Example : 2500000007 -
RequiredmaxFeePerGas string
Representation of the max fee per gas value
Example : 6655534951 -
RequiredmaxPriorityFeePerGas string
Representation of the max priority fee per gas value
Example : 1000000000
-
-
RequiredtransactionType string
Representation of the transaction type
Example : access-list-transaction
-
-
-