> ## 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".

# TokenFeeScheduleUpdate

At consensus, updates a token type's fee schedule to the given list of custom fees. If the target token type has no fee\_schedule\_key, resolves to `TOKEN_HAS_NO_FEE_SCHEDULE_KEY.` \*\*\*\* Otherwise, this transaction must be signed to the fee\_schedule\_key, or the transaction will resolve to `INVALID_SIGNATURE`. If the custom\_fees list is empty, clears the fee schedule or resolves to `CUSTOM_SCHEDULE_ALREADY_HAS_NO_FEES` if the fee schedule was already empty.

| Field | Type | Description |
| - | - | - |
| `token_id` | [TokenID](/reference/protobuf/basic-types/tokenid) | The token whose fee schedule is to be updated |
| `custom_Fees` | repeated [CustomFee](/reference/protobuf/token/customfees/customfee) | The new custom fees to be assessed during a CryptoTransfer that transfers units of this token |