⏸ Testnet indexer is temporarily on pause

Tonviewer and TonAPI services on testnet are off for maintenance. We plan to turn testnet back on within 24 hours.

DDoS again.
We are fixing

UPD: we had downtime from 12:04 to 12:30 Dubai time

API service is currently disrupted due to network issues following a DDoS attack. We are actively working to resume operations. Our apologies for the inconvenience. Please look out for further updates.

UPD Service is brought back to life.

We've been experiencing issues with crediting funds to the TON Console over the past few days.
The issue was related to an error in processing transactions by the payment provider involving payloads created by the MyTonWallet.

The payment provider has been corrected, all missed payments have been credited!
MyTonWallet has also fixed the error and will be updated.

Testnet API is temporary disabled. We are investigating the source of the problem.
UPD: Fixed.

[Fixed]

We encountered an issue with our indexing system that resulted in a halt to the indexing process. This problem occurred between 14:30 and 16:00 GST (Dubai time), which disrupted normal operations. To monitor the availability of TON API and other services, you can utilize the website tonstat.us for real-time status updates.

We have issues with showing past blockchain data via API.

Shortly new transactions will be available through API. We are working on restoring access to the past data.

All other functionality works as intended. That includes:
— Current state
— Sending transactions

New history is available, indexing current state too.
We are working on restoring archive history.

👨‍👨‍👦‍👦 Project Sharing

We've added the ability to share access to a project among users with equal rights.
You can try it out here - https://tonconsole.com/settings/edit-project

🚧 TonAPI Price Index Update

Today TonAPI team rolled out an update to the price index. Price index is used to display balances in our products: Tonkeeper, Tonkeeper Pro and Tonviewer.

During the upgrade displayed prices for some assets jumped by a few orders of magnitude. Users saw their balances displaying in billions for a few minutes. TonAPI team quickly identified the glitch and deployed the fix immediately.

We apologize to all the users for the confusion caused by this issue. We always strive for maximum accuracy of any information that TonAPI provides, however it is important to remember that all the data is provided as is. Prices in particular may be subject to high volatility and arbitrary delays.

There are many factors that may impact the displayed prices — for instance, low liquidity tokens price manipulation. If you make trade decisions based on the data offered by TonAPI or any other service, you need to apply your own judgement to make sure the information at hand is accurate and current.

We just released the first stable versions of the npm packages:
1. @ton-api/client — a new autogenerating client for working with TonAPI, compatible with the @ton/core library.
2. @ton-api/ton-adapter — an adapter for integrating @ton-api/client with the @ton/ton and @ton/core libraries, enabling the use of TonAPI functionality while maintaining the existing code structure.

You can check out the example of gasless transactiosns implementation using these libraries: https://github.com/tonkeeper/tonapi-js/blob/main/examples/gasless.ts

Network activity is higher than usual due to $DOGS minting. You may notice delays in transactions.

Over the past two days, the TONAPI service has been experiencing a significant DDoS attack. This has resulted in some customers encountering 403 errors in rare cases. We are actively addressing this issue and appreciate your patience as we work to resolve it. Thank you for your understanding.

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.