NFTs - apiTON

NFT items owned by an address, with display metadata resolved by apiton (off-chain JSON included).

Request. address (owner, .ton names allowed), collection_address (only this collection; empty = all), limit (≤ 100, default 10), offset.

Response. result — address, index, collection_address, content (raw on-chain), name, description, image, image_medium (resized https preview), content_url, lottie (gifts), domain (TON DNS), collection_name. Any metadata field may be empty.

Paging. total (int64 as a string) is set only when the page reached the end of the list. Items taken down by apiton are left out, so a page can hold fewer than limit items — keep paging by offset.

Errors (Connect JSON envelope {"code":…,"message":…})

Code	When
`invalid_argument` (400)	the owner or collection address cannot be parsed
`unavailable` (503)	the TON index failed — retry later

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200OK

application/json

Bodyapplication/json

Examples

SuccessOwner by .ton name (live, 2026-10-19)

{
    "result": [
        {
            "address": "UQDr5nMy8PFl1laCAc_vzecloxC4sVG5qjk9j6EsjDMFAVmh",
            "collection_address": "UQBDLUE8wS7K82cS_hCz8fnVVU4VgiQOqa5b1TFDDCIwKjkv",
            "content": {
                "uri": "https://s.getgems.io/nft/c/6286e4149e7aeee439741a29/118.json"
            },
            "index": "118"
        }
    ]
}

🔴500Server Error