Send XDC / ERC20 from account to account

/v3/xdc/transaction

2 credits per API call

Send XDC or Tatum supported ERC20 token from account to account.

Signing a transaction

When sending XDC, 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.

Alternatively, using the Tatum client library for supported languages.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
length ≤ 50000

Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format

string
enum
required

Currency of the transfer. ERC20 tokens are available only for mainnet use.

Allowed:
number
≥ 0

Nonce to be set to XDC transaction. If not present, last known nonce will be used.

string
required
length between 42 and 43

Blockchain address to send assets

fee
object

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

string
required

Amount to be sent.

string
required
length between 66 and 66

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

Responses

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