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:
previewWhy 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.