Update the recipient of the NFT auction fee

/v3/blockchain/auction/recipient

2 credits per API call

Update the recipient of the NFT auction fee.

This API is supported for the following blockchains:

  • BNB Smart Chain
  • Celo
  • Ethereum
  • Harmony
  • Klaytn
  • Polygon

Signing a transaction
When updating the recipient of the NFT auction, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.

Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the testnet of a blockchain.

For signing transactions on the mainnet, we strongly recommend that you use the Tatum Key Management System (KMS) and provide the signature ID instead of the private key in the API. Alternatively, you can use the Tatum JavaScript client.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
enum
required

Blockchain to work with.

Allowed:
string
required
length between 42 and 42

Address of the marketplace smart contract.

string
required
length between 42 and 42

Recipient address of the marketplace fee.

string
required
length between 66 and 66

Private key of sender address. Private key, or signature Id must be present.

number

The nonce to be set to the transaction; if not present, the last known nonce will be used

fee
object

Custom defined fee. If not present, it will be calculated automatically.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json