---
title: "Enable receiving asset on account"
method: POST
path: "/v3/algorand/asset/receive"
tags: ["Algorand - Tatum API"]
---

# Enable receiving asset on account

`POST /v3/algorand/asset/receive`

<h4>2 credits per API call.</h4><br/>
<p>Enable accepting Algorand asset on the sender account.<br/><br/>
This operation needs the private key of the blockchain address.
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,
<a href="https://github.com/tatumio/tatum-kms" target="_blank">Tatum KMS</a> 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.
</p>

## Request body

- union
  - ReceiveAlgorandAsset
    - `assetId` number, required — AssetID of the asset you wanna enable for the sender.
    - `fromPrivateKey` string, required — Private key of sender address. Private key, or signature Id must be present.
    - `fee` string — The transaction fee in Algos
  - ReceiveAlgorandAssetKMS
    - `from` string, required — Blockchain sender address.
    - `assetId` number, required — AssetID of the asset you wanna enable for the sender.
    - `fee` string — The transaction fee in Algos
    - `signatureId` string, uuid, required — Identifier of the private key associated in signing application. Private key, or signature Id must be present.
    - `index` number — If signatureId is mnemonic-based, this is the index to the specific address from that mnemonic.

## 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/revisions/8622ee4b8fae/schema)