Skip to main content
The TokenClaimAirdropTransaction allows an intended airdrop recipient to claim a pending token transfer, requiring signatures from both the receiver and transaction payer. When no auto-association slots are available, this transaction handles both the TokenAssociate and CryptoTransfer steps. If the receiver account has auto-association slots available, the token is automatically associated and transferred, making the claim transaction unnecessary. The receiver pays only the transaction fee, while the sender covers association and custom fees. Once claimed, the transfer is irreversible and removed from network state. All referenced pending airdrops must succeed for the transaction to complete.
  • Claimed airdrops result in token transfers recorded in the token_transfer_list in the transaction record.
  • Claimed pending airdrops are removed from the network state and cannot be claimed again.

Transaction Signing Requirements

  • The receiver account key.
  • The transaction fee payer account key if it differs from the sender.

Transaction Fees

  • Please see the transaction and query fees table for the base transaction fee.
  • Please use the Hedera fee estimator to estimate the cost of your transaction fee.
Reference: Token Airdrop Example
This transaction supports high-volume entity creation (HIP-1313). Setting setHighVolume(true) routes the transaction through dedicated high-volume throttle capacity with variable-rate pricing. Always pair this with setMaxTransactionFee() to cap your costs.