TON DocsTON Docs
OnboardingNodesApplicationsAPIsContractsSmart contractsTolkTolk languageTVMTON Virtual MachineFoundationsBlockchain foundations

Action types classification in TON Center API v3

An action describes an activity in a trace, such as a transfer, contract call, or NFT purchase. The type field identifies the activity, details contains type-specific fields, and success specifies the outcome.

Query action types

Use action_type on GET /actions to select types and exclude_action_type to omit types. Repeat the parameter to match each target type.

For example, to query for jetton transfer and burn actions for an account, replace <ACCOUNT_ADDRESS> with an account address in the following request:

curl --get "https://toncenter.com/api/v3/actions" \
  --data-urlencode "account=<ACCOUNT_ADDRESS>" \
  --data-urlencode "action_type=jetton_transfer" \
  --data-urlencode "action_type=jetton_burn"

To retrieve actions for a trace, use the trace_id parameter. To do the opposite, and include certain actions in a trace response, set include_actions=true on GET /traces.

By default, higher-level actions replace their component actions. For example, nft_purchase replaces its nft_transfer component, even when filtering for nft_transfer. Include both types to find purchases and standalone transfers.

Action types

Use these type names with action_type or exclude_action_type. Refer to the actions response schema for the fields in details.

Response-only type

extra_currency_transfer identifies a message carrying extra currencies. Query call_contract or ton_transfer, then select actions with this response type.

Contracts and currency

  • call_contract: Send a message that calls a smart contract.
  • contract_deploy: Deploy a smart contract to an account.
  • gasless_request: Submit a gasless transaction request.
  • tick_tock: Execute a system-triggered tick or tock transaction.
  • ton_transfer: Transfer Gram between accounts.

Jettons

  • jetton_burn: Burn jettons held by an owner.
  • jetton_mint: Mint jettons to a wallet.
  • jetton_swap: Asset swap through a decentralized exchange.
  • jetton_transfer: Transfer jettons between owners.

NFTs and auctions

  • auction_bid: Place a bid at an auction.
  • auction_outbid: Refund a previous bidder after a higher bid.
  • nft_cancel_auction: Cancel an NFT auction.
  • nft_cancel_sale: Cancel an NFT sale.
  • nft_discovery: Report an NFT's collection and item index.
  • nft_finish_auction: Finish an NFT auction.
  • nft_mint: Mint an NFT.
  • nft_purchase: Purchase an NFT.
  • nft_put_on_auction: List an NFT for auction.
  • nft_put_on_sale: List an NFT for sale at a fixed price.
  • nft_transfer: Transfer ownership of an NFT.
  • nft_update_sale: Update a sale's price or fees.
  • teleitem_cancel_auction: Cancel a collectible auction on Fragment.
  • teleitem_start_auction: Start a collectible auction on Fragment.

DNS

  • change_dns: Set a DNS record value.
  • delete_dns: Delete a DNS record.
  • dns_purchase: Purchase a DNS name.
  • dns_release: Release the balance of a DNS name contract.
  • renew_dns: Renew a DNS name.

Liquidity, staking, and elections

  • dex_deposit_liquidity: Deposit assets into a liquidity pool.
  • dex_withdraw_liquidity: Withdraw assets from a liquidity pool.
  • tonco_deploy_pool: Deploy a concentrated liquidity pool.
  • stake_deposit: Deposit stake.
  • stake_withdrawal: Withdraw stake.
  • stake_withdrawal_request: Request a stake withdrawal.
  • election_deposit: Deposit stake for a validator election.
  • election_recover: Recover stake from a validator election.

Subscriptions

  • subscribe: Create a subscription.
  • unsubscribe: Cancel a subscription.

Multisig and vesting

  • multisig_create_order: Create a multisig order.
  • multisig_approve: Approve a multisig order.
  • multisig_execute: Execute a multisig order.
  • vesting_add_whitelist: Add accounts to a vesting contract allowlist.
  • vesting_send_message: Send a message from a vesting contract.

Cocoon

  • cocoon_client_change_secret_hash: Change a client's secret hash.
  • cocoon_client_increase_stake: Increase a client's stake.
  • cocoon_client_register: Register a client.
  • cocoon_client_request_refund: Request a client refund.
  • cocoon_client_top_up: Top up a client's balance.
  • cocoon_client_withdraw: Withdraw funds from a client.
  • cocoon_grant_refund: Grant a client refund.
  • cocoon_proxy_charge: Charge a client through a proxy.
  • cocoon_proxy_payout: Pay the proxy's owner.
  • cocoon_register_proxy: Register a proxy.
  • cocoon_unregister_proxy: Unregister a proxy.
  • cocoon_worker_payout: Pay the worker's owner.

Bitcoin bridge

  • tgbtc_burn: Burn bridge tokens.
  • tgbtc_burn_fallback: Burn with partial details.
  • tgbtc_dkg_log_fallback: Completion of distributed key generation.
  • tgbtc_mint: Mint bridge tokens.
  • tgbtc_mint_fallback: Mint with partial details.
  • tgbtc_new_key: Create a bridge key.
  • tgbtc_new_key_fallback: Bridge key creation with partial details.

EVAA

  • evaa_supply: Supply assets.
  • evaa_withdraw: Withdraw assets.
  • evaa_liquidate: Liquidate a position.

JVault

  • jvault_claim: Claim staking rewards.
  • jvault_stake: Deposit into staking.
  • jvault_unstake_request: Request to withdraw from staking.
  • jvault_unstake: Withdrawal from staking.

SwapCoffee

  • coffee_create_pool: Create a liquidity pool.
  • coffee_create_pool_creator: Create a pool creator contract.
  • coffee_create_vault: Create a vault.
  • coffee_mev_protect_failed_swap: Record a failed swap under maximal extractable value (MEV) protection.
  • coffee_mev_protect_hold_funds: Hold funds under MEV protection.
  • coffee_staking_claim_rewards: Claim staking rewards.
  • coffee_staking_deposit: Deposit into staking.
  • coffee_staking_withdraw: Withdraw from staking.

LayerZero

  • layerzero_receive: Receive a packet.
  • layerzero_commit_packet: Commit a packet.
  • layerzero_dvn_verify: Verify a packet through a verifier.
  • layerzero_send: Send a packet.
  • layerzero_send_tokens: Send tokens.

Other

  • unknown: Unclassified activity in a trace.

Classification presets

The supported_action_types field works with either version presets or broad category shortcuts, not with specific action types. If neither the supported_action_types field nor the X-Actions-Version header is supplied, the following endpoints that support both default to latest: GET /actions, GET /traces, GET /pendingActions, and GET /pendingTraces. The header takes priority over the field.

The v1 version presets are always included in the list, even when an explicit supported_action_types value is provided and replaces latest. Category shortcuts extend that baseline and do not filter results to the category. For example, supported_action_types=jettons also supports the other v1 types.

Repeat supported_action_types to combine selections. For instance, supported_action_types=latest&supported_action_types=tgbtc includes the default set and the tgbtc types. Unlike GET /traces, the action_type field in GET /actions selects matching types independently of the supported_action_types list. Yet, supported parent actions still suppress their components.

On this page