/v3/one/transaction

2 credits per API call

Send ONE from account to account.

The default shard 0 is used for the sender and the recipient.

Signing a transaction
When sending ONE, 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.

{
  "amount": "100000",
  "currency": "ONE",
  "to": "0x687422eEA2cB73B5d3e242bA5456b782919AFc85",
  "fromPrivateKey": "0x05e150c73f1920ec14caa1e0b6aa09940899678051a78542840c2668ce5080c2",
  "fee": {
    "gasPrice": "20",
    "gasLimit": "40000"
  },
  "data": "4d79206e6f746520746f2074686520726563697069656e74"
}

{
  "txId": "c83f8818db43d9ba4accfe454aa44fc33123d47a4f89d47b314d6748eb0e9bc9"
}