Mintless jettons support

TONAPI supports mintless jettons as a part of bigger standard for jettons with custom payload and init data.

When you are requesting jetton balances for an account and want to get mintless jettons transparently, you should use the custom_payload parameter in the supported_extension field in the request. For example, this link or direct jetton info this link:

    {
      "balance": "1000000000",
      "wallet_address": {
        "address": "0:405171f583a9e39e22ae9d8394769bc6e37299c59332012a51693b4d606780f3"
      },
      "jetton": {
        "address": "0:fa67d0c7739331fbc3c8f08e018c65f47763616a969100ad760a0b2dc1e36832",
        "name": "Mintless Points",
        "symbol": "Points",
        "decimals": 9,
        "image": "https://cache.tonapi.io/imgproxy/DmmPn6dWmsmBgSMVbvjbhIDCChLWI3RmqDJ71whxYBA/rs:fill:200:200:1/g:no/aHR0cHM6Ly9pLmliYi5jby9TS010TlRHL21pbnRsZXNzLnBuZw.webp",
        "custom_payload_api_uri": "https://claim-api.tonapi.io/jettons/EQD6Z9DHc5Mx-8PI8I4BjGX0d2NhapaRAK12CgstweNoMint"
      },
      "extensions": [
        "custom_payload"
      ]
    }

How to Support Mintless Jettons in Your Dapp

1. Request balances with ?supported_extensions=custom_payload.
2. Check if data["extensions"] contains "custom_payload" for the jetton.
3. If it contains and you want to autoclaim on transaction, when your dapp asks the user to send an outgoing jetton transfer via TonConnect, request custom payload and state init via the API: https://tonapi.io/v2/jettons/0:fa67d0c7739331fbc3c8f08e018c65f47763616a969100ad760a0b2dc1e36832/transfer/UQBDaa8UGaMVKiT8TKXiaJqlyWLmx-MoHYvT_wzHEpdUnIss/payload.
4. Add the received data to the message in your TonConnect request.
5. That's it. Now you support mintless jettons!

🔔 Building TMA with TON API 🔔

Hello, friends! We’re excited to announce an upcoming online workshop led by Tonkeeper developer Maksim Voloshinskii for the "Ton Apps" track in the Hackers League Hackathon! In this session, Maksim will show how to build decentralized applications (dApps) with TON API, sharing essential integration insights and answering participants' questions.

✨ What you can win: Cash prizes, free access to TON API tiers, and exclusive mentorship from the Tonkeeper team.
📅 Date & Time: November 12, 14:00 UTC
📌 Hackathon runs until November 24, 2024
🚀 Ready to dive into dApp development? Join in, ask questions, explore TON API, and launch your projects!

🔗 Useful Links for Participants:
Workshop Materials
Participant Chat
Project Submission Form
YouTube Broadcast
✨ Start your journey with TON API here: tonconsole.com

Good news, everyone!

We are excited to announce the launch of our webhook service.
(Actually, there might still be some issues like delivery delays, but the API is stabilized.)

What is it and why do you need it?
TON is renowned for its scalability, meaning more transactions and blocks are added to the blockchain every second. In last year's stress tests, a record of 100,000 transactions per second was set. This means the blockchain generated over 100 megabytes of blocks per second or about a gigabit of incoming traffic if you want to view the entire blockchain. Of course, not every service needs to view all transactions in all blocks to find valuable insights.
To solve this problem, we are launching a webhook service that allows you to subscribe only to the data you need. Our service will attempt to deliver messages at increasing intervals until your server returns a 200 response.

Current subnoscription options:

1. Subnoscription to specific accounts - You can subscribe to a million accounts, and if a transaction occurs on any of them, we will notify you. Charges are based on the number of monitored account-days and each event.

2. Subnoscription to specific opcodes of incoming messages - If any account receives an incoming message with such an opcode, we will notify you. Up to 100 opcodes per account. Charges are based on the number of events.

3. Subnoscription to new accounts in the network - Don't require denoscription. Charges only for the number of messages.

4. Subnoscription to the mempool - We send all externals we see before they are included in the blockchain. Charges for each sent message, and no retries. If your server was unavailable, we will not attempt to resend.

Try it! Or read the docs first!

We welcome any feedback in comments to this post.

TonApi V2: Jetton Logo Field Migration

We have made changes to the structure of Jetton data returned by TonApi V2, affecting the way logos are handled. This is particularly important for users working with Jetton images.

The migration will be completed on January 15, 2025

What has changed:
1. A new field preview has been added to the JettonInfo object. It contains a link to a cached image of the Jetton logo, specifically prepared for fast and convenient display.
2. The field metadata.image in the JettonInfo object temporarily returns the same cached image as preview. Once the migration is complete, this field will start returning the original link to the logo from the Jetton metadata.

We now recommend to display logos using the field: preview

Why are we migrating:
The goal of the migration is to resolve the mismatch between the original metadata and what our API currently provides. At present, metadata.image returns a cached image instead of the original link. After the migration, the metadata will fully reflect the original data, without any modifications.

This eliminates the need for developers to parse contract cells to retrieve original image links.

Affected Schema: JettonInfo
Affected Methods:
• getJettonInfo (/v2/jettons/{account_id})
• getJettons (/v2/jettons)
• getJettonInfosByAddresses (/v2/jettons/_bulk)

JettonInfo:
  type: object
  required:
    - mintable
    - total_supply
    - metadata
    - verification
    - holders_count
  properties:
    metadata: # <- will match the original metadata after migration
      $ref: '#/components/schemas/JettonMetadata'
    preview: # <- new field
      type: string
      example: "https://cache.tonapi.io/images/jetton.jpg"
    # ... other fields

Backward compatibility:
This change does not break existing integrations—your applications will continue to work without modifications. However, the image URLs for Jettons will point to the original addresses, which may affect image loading speed and the privacy of the end user.

TonApi V2: Jetton Logo Field Migration Completed

The migration of the Jetton logo field in TonApi V2 has been successfully completed today.

Now, metadata.image returns the original logo link from the Jetton metadata, while the preview field continues to provide a cached version for display.

If you haven’t yet, update your integration to use preview for displaying Jetton logos.

Everything else remains unchanged, and no action is required for existing integrations.

Introducing TONAPI Airdrop: Scalable Token Distribution on TON

The TONAPI Airdrop, developed by the Tonkeeper team, streamlines Jetton distribution for projects on TON, supporting up to 10 million claims. Perfect for gaming and community rewards, it simplifies large-scale token drops.

Why Use TONAPI Airdrop?

Streamlined Distribution: Upload a .csv, select your token, and launch instantly.
Scalable & Secure: Supports up to 10 million claims with built-in security.
Efficient for Developers: No complex minting required, making token distribution seamless.

Airdrops in Action: Memhash

Memhash is the first project to adopt TONAPI Airdrop to increase engagement, simplify token rewards, and strengthen its in-game economy.

Learn more about TONAPI Airdrop: tonapi.io/airdrop

Get high TONAPI limits in your dApps for free

You already know our @ton-api/client library — a client for building advanced TON dApps. Now, we're happy to announce a new feature that grants high TONAPI limits for free.

This upgrade enables cost-free TON API usage within dApps running in the Tonkeeper built-in browser (mobile) and standard browsers with the Tonkeeper extension installed.

To check if this feature is available, verify that the window.tonapi object exists in your browser.

How it works →

The Testnet API will undergo planned maintenance on April 4, 2025, from 08:00 UTC to 12:00 UTC. It will be unavailable during this time.

Tracking Transactions on TON Just Got Easier! 🎉

Tracking external transactions (external-in) on the TON blockchain was challenging for all of us due to minor metadata differences.

Now TonAPI solves this with the normalized hash. With this method, tracking transactions is simple and reliable.

We've prepared clear examples to get you started:
- Tracking transactions from TonConnect for dApps
- Tracking manually constructed external messages

See code examples →

We’re excited to share this improvement, and soon more ecosystem tools will support it too!

We wrote an article to explain in more detail how external-in normalization works and how to use it to track transactions reliably. Read the article

🛠 wallet.ton.org runs on TON API

TON Core team becomes the latest customer of our development platform TON API, among @wallet, Trust Wallet, Tonstakers and many other big players in TON.

The latest upgrade of wallet.ton.org relies on TON API for its key features: token and NFT balances, and price feeds.

We are delighted to support and grow the TON ecosystem with our integrated approach to infrastructure, open standards, partnerships and deep product integration in Tonkeeper, Tonkeeper Pro and Ton Console.

📝 Sign Arbitrary Data with TON Connect

The latest update to our TON Connect implementation introduces a powerful new feature: the ability to sign arbitrary data — from plain text and binary blobs to BOC (cell) format.

This unlocks new use cases in the TON ecosystem: secure off-chain flows, verifiable signatures, and advanced on-chain logic — all through the familiar TON Connect interface.

Now supported in the latest versions of Tonkeeper on iOS and Android.

Explore the guide and start building →

💻TONAPI YouTube Contest — Now Open

We are inviting developers to create technical YouTube videos showcasing real use cases with TONAPI, from tutorials and code walkthroughs to project demos and tooling comparisons.

The top 5 videos will split a 5,000 USDT prize pool (Bitrefill Gift Card).

Winning entries will also receive visibility on Tonkeeper social channels, TONAPI discount codes, potential dApp Browser integrations, and invitations to our exclusive mentorship program.

👉 Submit by emailing contest@tonkeeper.com with subject “TONAPI Contest”

📆Submissions are open until July 18.

Full details

🏆TONAPI YouTube Contest — Winners Announced

Thank you to everyone who submitted a video for the TONAPI YouTube Contest. We loved seeing the range of projects built with TONAPI.

🥳Congratulations to the 5 winners who will share the 5,000 USDT prize pool in the form of Bitrefill gift cards, with 1,500 USDT awarded to first place.

Winning entries:

1st: link
2nd: link
3rd: link
4th: link
5th: link

We appreciate the effort from every participant. The number of submissions exceeded our expectations, so we needed a bit more time to review them all. Thank you for your patience.

📨Winners will be contacted by email to arrange prize distribution.

We look forward to seeing more builds with TONAPI.

Download Tonkeeper tonkeeper.com
Mini app | 𝕏 | ru | فارسی | 中文 | uz

Technical update about external messages for wallets v4

Tomorrow ~10:00 UTC we will deploy an emergency update that breaks backward compatibility. The decoded external message body for wallets_v4r2 will now use a SumType for the payload.
You can see the difference at the following two URLs:

https://dev.tonapi.io/v2/blockchain/transactions/3d3ad440cd5d1c5bb089695338f250d19707659e4444c98756fcc0d444558346 - new version
https://tonapi.io/v2/blockchain/transactions/3d3ad440cd5d1c5bb089695338f250d19707659e4444c98756fcc0d444558346 - old version

It doesn’t affect you if you haven’t used the decoded_body field for external messages in raw transactions or traces.

We plan maintenance work today at 14:00 UTC for approximately less than an hour. The tonconsole.com admin panel and analytics queries may be unavailable during this time. The functionality of the main API will not be affected.

We apologize for the prolonged migration. The service has been restored.

Dear users,

Please note that on October 20, the liteserver error codes in the service at https://tonconsole.com/tonapi/liteservers will be updated.
Alongside the standard liteserver error codes (such as 651, -400, etc.), the service may return additional codes.
Specifically, error code 5556 will be REPLACED with 228 (rate limit exceeded) for consistency.
Proper handling of these error codes is crucial for maintaining stable operation of client applications.
To prevent rate limit errors, consider implementing a rate limiter on the client side, configured slightly below the plan's maximum threshold.