- If the provided account is not found, the transaction will resolve to
INVALID_ACCOUNT_ID. - If the provided account has been deleted, the transaction will resolve to
ACCOUNT_DELETED. - If any of the provided tokens is not found, the transaction will resolve to
INVALID_TOKEN_REF. - If any of the provided tokens has been deleted, the transaction will resolve to
TOKEN_WAS_DELETED. - If an association between the provided account and any of the tokens already exists, the transaction will resolve to
TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT. - If the provided account’s associations count exceeds the constraint of maximum token associations per account, the transaction will resolve to
TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED. - On success, associations between the provided account and tokens are made and the account is ready to interact with the tokens.
There is currently no limit on the number of token IDs that can be associated with an account (reference HIP-367). Still, you can see
TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED responses for pre-HIP-367 transactions.- The key of the account the token is being associated to
- Transaction fee payer account key
- Please see the transaction and query fees table for the base transaction fee
- Please use the Hedera fee estimator to estimate your transaction fee cost
Methods
| Method | Type | Description | Requirement |
|---|---|---|---|
setAccountId(<accountId>) | AccountId | The account to be associated with the provided tokens | Required |
setTokenIds(<tokens>) | List <TokenId> | The tokens to be associated with the provided account | Required |