---
title: "Send Algos to an Algorand account"
method: POST
path: "/v3/algorand/transaction"
tags: ["Algorand - Tatum API"]
---

# Send Algos to an Algorand account

`POST /v3/algorand/transaction`

**2 credits per API call**

Send Algos from one Algorand address to the other one.

**Signing a transaction**

When sending Algos, 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

- union
  - TransferAlgorandBlockchain
    - `from` string, required — The blockchain address of the sender
    - `to` string, required — The blockchain address of the recipient
    - `fee` string, required — The transaction fee in Algos
    - `amount` string, required — The amount to send in Algos
    - `note` string — The note for the recipient; must not contain spaces
    - `fromPrivateKey` string, required — Private key of sender address. Private key, or signature Id must be present.
  - TransferAlgorandBlockchainKMS
    - `from` string, required — The blockchain address of the sender
    - `to` string, required — The blockchain address of the recipient
    - `fee` string — The transaction fee in Algos
    - `amount` string, required — The amount to send in Algos
    - `note` string — The note for the recipient; must not contain spaces
    - `index` number — If signatureId is mnemonic-based, this is the index to the specific address from that mnemonic.
    - `signatureId` string, uuid, required — Identifier of the private key associated in signing application. 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.
- `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)