addressBook
endpoint retrieves information about a specific address from the TON blockchain’s address book. This can be useful for identifying known entities or contracts on the network.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
TON pricing is the same for full, archive, v2, v3There’s no difference between a full node an archive node in data availability or pricing.
All data is always available and all node requests are consumed as 1 request unit.
All data is always available and all node requests are consumed as 1 request unit.
Parameters
address
(string, required) — The address to look up in the address book. This should be a raw address format. Example:0:ed1691307050047117b998b561d8de82d31fbf84910ced6eb5fc92e7485ef8a7
.
Response
name
(string) — The name associated with the address, if available.description
(string) — A description of the address or the entity it represents.icon
(string) — URL of an icon associated with the address or entity.website
(string) — Website associated with the address or entity.address
(string) — The queried address, confirming the lookup.
Use case
TheaddressBook
endpoint can be used in various scenarios:
- Wallet applications can use it to display human-readable names and descriptions for known addresses.
- Block explorers can enhance their UI by showing additional information about significant addresses.
- DApps can use it to verify if they’re interacting with known, trusted contracts or entities.
Query Parameters
The address to look up in the address book
Response
200 - application/json
Successful response
The response is of type object
.