---
title: "Send VeChain from account to account"
method: POST
path: "/v3/vet/transaction"
tags: ["VeChain - Tatum API"]
---

# Send VeChain from account to account

`POST /v3/vet/transaction`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/vet/transaction`
- Auth: API key in header `x-api-key`

/v3/vet/transaction

#### 10 credits per API call.

  

Send VET from account to account. Fee for the transaction is paid in VTHO.  
  
This operation needs the private key of the blockchain address. Every time the funds are transferred, the transaction must be signed with the corresponding private key. No one should ever send it's own private keys to the internet because there is a strong possibility of stealing keys and loss of funds. In this method, it is possible to enter privateKey or signatureId. PrivateKey should be used only for quick development on testnet versions of blockchain when there is no risk of losing funds. In production, [Tatum KMS](https://github.com/tatumio/tatum-kms) should be used for the highest security standards, and signatureId should be present in the request. Alternatively, using the Tatum client library for supported languages.

## Request body

- union
  - TransferVetBlockchain
    - `to` string, required: Blockchain address to send assets
    - `amount` string, required: Amount to be sent in VET
    - `fromPrivateKey` string, required: Private key of sender address. Private key, or signature Id must be present.
    - `data` string: Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format
    - `fee` object: Custom defined fee. If not present, it will be calculated automatically.
      - `gasLimit` string, required: Gas limit for transaction.
  - TransferVetBlockchainKMS
    - `to` string, required: Blockchain address to send assets
    - `amount` string, required: Amount to be sent in VET
    - `signatureId` string, uuid, required: Identifier of the private key associated in signing application. Private key, or signature Id must be present.
    - `data` string: Additional data that can be passed to a blockchain transaction as a data property; must be in the hexadecimal format
    - `fee` object: Custom defined fee. If not present, it will be calculated automatically.
      - `gasLimit` string, required: Gas limit for transaction.

## Response `200`

OK

- TransactionHash
  - `txId` string, required: The hash (ID) of the transaction

## 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.dev/tatum/apis/blockchain.md) - [All operations](https://skmtc.dev/tatum/apis/blockchain/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/blockchain/revisions/f9623a85f420?raw)