Skip to main content
GET
/
analytics
/
stablecoins
/
transfers
Stablecoin Transfers - Aggregated Insights
curl --request GET \
  --url https://api.amberdata.com/blockchains/analytics/stablecoins/transfers \
  --header 'x-api-key: <api-key>'
{
  "status": 200,
  "title": "OK",
  "description": "Successful request",
  "payload": {
    "data": [
      {
        "assetAddress": "0x94b008aa00579c1307b0ef2c499ad98a8ce58e58",
        "assetName": "Tether USD",
        "assetSymbol": "USDT",
        "blockchain": "optimism-mainnet",
        "burnVolume": "1038393.596801",
        "mintVolume": "328456.31803",
        "numberOfBurns": "26",
        "numberOfMints": "10",
        "numberOfTransfers": "4137",
        "numberOfUniqueReceivers": "460",
        "numberOfUniqueSenders": "395",
        "timestamp": "2025-07-25T01:00:00Z",
        "transferVolume": "612098.87144"
      }
    ],
    "metadata": {}
  }
}
If the startDate and endDate query parameters are not provided, the API will return the data from the previous 24 hrs of data.
If the blockchain query parameter is not provided, the API will return data from all of the supported chains.
Contract addresses for an asset are unique per blockchain. If you would like to see the analytics for a specific asset, say USDC across all chains, use the assetSymbol query parameter and omit the blockchain query parameter.

Authorizations

​
x-api-key
string
header
required

Query Parameters

​
assetSymbol
string

[optional] The symbol of the asset to filter the dataset by

​
assetAddress
string

[optional] The contract address of the asset to filter the dataset by

​
startDate
string

[optional] The oldest date to filter the dataset by (inclusive)

​
endDate
string

[optional] The latest data to filter the dataset by (exclusive)

​
blockchain
enum<string>

[optional] The name slug of the chain to filter the dataset by

Available options:
arbitrum-mainnet,
avalanche-mainnet,
base-mainnet,
bnb-mainnet,
ethereum-mainnet,
polygon-mainnet,
optimism-mainnet,
tron-mainnet

Response

200 - application/json

Successful request

​
status
integer
required

HTTP status code

Example:

200

​
title
string
required

Response status title

Example:

"OK"

​
description
string
required

Response description

Example:

"Successful request"

​
payload
object
required