> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# TokenAssociate

Associates the provided account with the provided tokens. Must be signed by the provided Account's key.

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.

## TokenAssociateTransactionBody

| Field | Type | Description |
| - | - | - |
| `account` | [AccountID](/reference/protobuf/basic-types/accountid) | The account to be associated with the provided tokens |
| `tokens` | repeated [TokenID](/reference/protobuf/basic-types/tokenid) | The tokens to be associated with the provided account. In the case of `NON_FUNGIBLE_UNIQUE` Type, once an account is associated, it can hold any number of NFTs (serial numbers) of that token type. |