---
title: "Send AVAX or fungible tokens (ERC-20) from account to account"
method: POST
path: "/v3/avalanche/transaction"
tags: ["Avalanche - Tatum API"]
---

# Send AVAX or fungible tokens (ERC-20) from account to account

`POST /v3/avalanche/transaction`

/v3/avalanche/transaction

**2 credits per API call**

Send AVAX or Tatum-supported fungible tokens (ERC-20) from account to account.

**NOTE:** Sending the fungible tokens is supported only on the mainnet.

**Signing a transaction**  
When sending AVAX, 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)](https://github.com/tatumio/tatum-kms) and provide the signature ID instead of the private key in the API. Alternatively, you can use the [Tatum JavaScript client](https://github.com/tatumio/tatum-js/tree/v2).

## Request body

- TransferAvalancheBlockchain
  - `data` string — Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format
  - `nonce` number — Nonce to be set to Avalanche transaction. If not present, last known nonce will be used.
  - `to` string, required — Blockchain address to send assets
  - `currency` 'AVAX', required — Currency to transfer from Avalanche Blockchain Account.
  - `fee` object — Custom defined fee. If not present, it will be calculated automatically.
    - `gasLimit` string, required — Gas limit for transaction in gas price.
    - `gasPrice` string, required — Gas price in Gwei.
  - `amount` string, required — Amount to be sent.
  - `fromPrivateKey` string, required — Private key of sender address. Private key, or signature Id must be present.

## Response `200`

OK

- union
  - TransactionHash
    - `txId` string, required — The hash (ID) of the transaction
  - SignatureId
    - `signatureId` string, uuid, required — The internal Tatum ID of the prepared transaction for Key Management Sysytem (KMS) to sign<br/>This is different from the <code>signatureId</code> parameter that you provided in the request body. The <code>signatureId</code> parameter in the request body specifies the signature ID associated with the private key in KMS.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403` — Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.
- `500` — Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/versions/8622ee4b8fae/schema)