TON – /v3/actions Does Not Return Jetton Transfers

When working with the TON API v3 Indexer via Tatum, you may notice that requests to the /v3/actions endpoint with filters for action_type=jetton_transfer return empty results.

Example Request:

curl --location 'https://ton-mainnet.gateway.tatum.io/api/v3/actions?account=0%3A488437deaf3da472bc56c77856faa42f1a55ce19387272dc468dc41062e148e4&start_utime=1757077488&action_type=jetton_transfer&include_accounts=false&limit=10&offset=0&sort=desc'\
--header 'x-api-key: {YOUR_API_KEY}'
//Response:
{
  "actions": [],
  "address_book": {},
  "metadata": {}
}

Why This Happens

This is expected behaviour.

Currently, the TON /v3/actions endpoint does not classify or surface jetton_transfer actions. These transfers are handled separately by the TON indexer’s EventClassifier module, which is not configured to include them in generic /actions queries.

How to Retrieve Jetton Transfers

Instead of using /v3/actions endpoint, jetton transfers can be queried through the dedicated jetton endpoints /api/v3/jetton/.* .

Example Request:

curl --location 'https://ton-mainnet.gateway.tatum.io/api/v3/jetton/transfers?owner_address=0%3A488437deaf3da472bc56c77856faa42f1a55ce19387272dc468dc41062e148e4&start_utime=1757077488&limit=10&offset=0&sort=desc' \
  --header 'x-api-key: {YOUR_API_KEY}'
//Response:
{
    "jetton_transfers": [
        {
            "query_id": "6083770387389331657",
            "source": "0:F884BC54C8B21C8A16C74AEE6294E80FEDBAC2B9C087FA9897773B3DB1DD0B7E",
            "destination": "0:488437DEAF3DA472BC56C77856FAA42F1A55CE19387272DC468DC41062E148E4",
            "amount...

Roadmap & Future Plans

At this time, there are no immediate plans to include jetton transfers in the /v3/actions endpoint. The TON specialized jetton endpoint give developers access to more detailed, jetton-specific data rather than mixing it into /v3/actions.

That said, this may be revisited in the future, and we’ll provide updates in our changelog if this changes.

Summary

1. /v3/actions does not return jetton transfers (expected behaviour).
2. Use the /api/v3/jetton/.* endpoints for jetton-specific data.
3. This provides more detailed and accurate information than the generic /actions feed

📘

Note

Endpoint details are available at TON API Reference.