---
title: "Set the contract address of an ERC-20, ERC-20-equivalent, or TRC-10 token"
method: POST
path: "/v3/offchain/token/{name}/{address}"
tags: ["Blockchain operations"]
---

# Set the contract address of an ERC-20, ERC-20-equivalent, or TRC-10 token

`POST /v3/offchain/token/{name}/{address}`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/offchain/token/{name}/{address}`
- Auth: API key in header `x-api-key`

/v3/offchain/token/{name}/{address}

**2 credits per API call**

Set the contract address of an ERC-20, ERC-20-equivalent (for example, BEP-20, HRM-20, and so on), or TRC-10 token to be able to communicate with the smart contract.

After creating and deploying the token to the blockchain, the smart contract address is generated and must be set within Tatum. If the address is not set, the Tatum platform will not be able to detect incoming deposits of the tokens and transfer the tokens from virtual accounts to blockchain addresses.

**NOTE:**

*   For **Algorand**, the contract address is the asset ID (`assetId`), for example, `55351976`.
*   For **TRON**, the contract address is the token ID (`tokenId`), for example, `1234567`.

## Path parameters

- `address` string, required
- `name` string, required

## Response `204`

OK

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