Skip to main content
This guide walks you through your first calls to the Data API. By the end, you’ll understand the request format, response structure, and key fields for three flagship endpoints — one for addresses, one for transfers, and one for tokens.
You’ll need an API key. All requests require a Bearer token. Sign up at app.range.org to generate one for free.

Authentication

Every Data API request uses the same authentication pattern. Pass your API key in the Authorization header:
Base URL: https://api.range.org
Keep your API key server-side. Never expose it in client-side code or public repositories.

1. Look Up an Address

The Get Address Information endpoint is the most common starting point. It returns labels, entity attribution, and metadata for any address across 18+ supported networks. Try it with Circle’s CCTP program on Solana:

Key Response Fields


2. Get Token Transfers

The Get token transfers endpoint returns cross-chain and same-chain transfers (IBC, CCTP, bridges, and more) for an address, with cursor-based pagination. Try it against the same address:

Key Response Fields

GET /v2/transfers supports dozens of filters — token_symbols, bridges, min_usd/max_usd, start_time/end_time, and more. See the endpoint reference for the full list.

3. Get a Token’s Total Supply

The Get total supply for a token endpoint returns current supply and decimals for any token. Try it with USDC on Solana:

Key Response Fields


Common Errors


What’s Next

Authentication

API keys, rate limits, and security best practices.

Data API Overview

See what you can build across addresses, networks, protocols, and stablecoins.

Supported Chains

The full list of networks the Data API covers.

Get Support

Questions? Our team is here to help.
Last modified on July 16, 2026