GET
https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3
/
nft
/
transfers
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/nft/transfers
{
  "transfers": [
    {
      "nft": {
        "address": "<string>",
        "collection": {
          "address": "<string>"
        }
      },
      "from": {
        "address": "<string>"
      },
      "to": {
        "address": "<string>"
      },
      "transaction": {
        "hash": "<string>",
        "time": 123
      },
      "value": "<string>"
    }
  ]
}

The nft/transfers endpoint retrieves a list of NFT (Non-Fungible Token) transfers from the TON blockchain. This endpoint allows you to fetch information about NFT transfer activities and provides options for filtering, pagination, and sorting.

Get you own node endpoint today

Start 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, v3

There’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.

​
Parameters

  • direction (string, required) — The direction of transfers to retrieve. Possible values: in, out, or both. Default: both.
  • limit (integer, optional) — The maximum number of transfers to return. Default: 128.
  • offset (integer, optional) — The number of transfers to skip before starting to return results. Default: 0.
  • sort (string, optional) — The sorting order of the transfers. Possible values: asc (ascending) or desc (descending). Default: desc.

​
Response

  • transfers (array) — An array of NFT transfer objects, each containing:
    • nft (object) — Information about the transferred NFT:
      • address (string) — The address of the NFT item.
      • collection (object) — Information about the collection:
        • address (string) — The address of the collection.
    • from (object) — Information about the sender:
      • address (string) — The address of the sender.
    • to (object) — Information about the recipient:
      • address (string) — The address of the recipient.
    • transaction (object) — Information about the transaction:
      • hash (string) — The hash of the transaction.
      • time (integer) — The timestamp of the transaction.
    • value (string) — The value of the transfer (if any).

​
Use case

The nft/transfers endpoint is useful for various applications that need to track or analyze NFT transfer activities on the TON blockchain:

  1. NFT marketplaces can use this to display recent sales or transfers of NFTs.
  2. Wallet applications can show users their history of NFT acquisitions and disposals.
  3. Analytics platforms can track NFT transfer patterns, popular collections, and market trends.
  4. Developers can use this endpoint to build notification systems for NFT transfers.
  5. Collectors can monitor transfers of specific NFTs or within particular collections.
  6. Compliance tools can use this data to track the provenance of NFTs.

Query Parameters

​
direction
enum<string>
default:both
required

The direction of transfers to retrieve

Available options:
in,
out,
both
​
limit
integer
default:128

The maximum number of transfers to return

​
offset
integer
default:0

The number of transfers to skip before starting to return results

​
sort
enum<string>
default:desc

The sorting order of the transfers

Available options:
asc,
desc

Response

200 - application/json

Successful response

The response is of type object.