apiTON
A narrow-purpose API provider at apiton.org for specialised TON services: .ton domain resolution, +888 anonymous numbers, DNS-infrastructure tooling and identity primitives on TON.
Aliases: apiton.org, api ton, api-ton
apiTON (apiton.org) is a narrow-purpose API provider for TON, focused on names and identity infrastructure: resolving .ton domains to wallet addresses, reverse resolution, working with anonymous +888 numbers (TON numbers sold on Fragment) and verifying that a number or a domain belongs to a given account.
Why a dedicated API
The base TON DNS operations are technically reachable through TonAPI or Toncenter — they all boil down to get-methods on the NFT collection EQC3dN…. But producing the address EQAv… from the string durov.ton, or enumerating every .ton domain owned by an address, over the raw API is awkward: you have to derive the item index from the domain name per TEP-81, call a get-method, parse a cell. apiTON returns that in a single REST call.
What it covers
.ton→ address resolution and the reverse direction.- Free-domain search with suggestions.
- Work with +888 TON numbers — which numbers belong to an account, is the subscription active.
- Owner identity — a short path from a Telegram account or a TON address to its canonical name.
Where it shows up
- Telegram bots that intercept upgraded gifts and collectible drops — they need a fast “who sent this NFT, what name is it tied to”.
- dApps that authenticate via a
.tondomain instead of a raw wallet address — TON Connect plus apiTON for the human-readable name. - Services that work with TON numbers and Telegram subscriptions.
How it differs from TonAPI
TonAPI is a general-purpose gateway: wallets, jettons, NFTs, events. apiTON is a domain-specific module over the subset of data that touches names and identity. A typical stack is “TonAPI plus apiTON for DNS tasks”, not “one or the other”.