Skip to main content

Your First API Call

Let’s fetch information about a Solana address in three simple steps:
1

Get Your API Key

Sign up at app.range.org and generate your free API key from the dashboard.
2

Make Your First Request

Query the Circle CCTP address on Solana:
curl -X GET "https://api.range.org/v1/address?address=CCTPiPYPc6AsJuwueEnWgSgucamXDZwBd53dQ11YiKX3&network=solana" \
  -H "X-API-KEY: your_api_key_here"
3

Explore the Response

You’ll receive comprehensive address information including labels, network, and entity details.
{
  "address": "CCTPiPYPc6AsJuwueEnWgSgucamXDZwBd53dQ11YiKX3",
  "network": "solana",
  "labels": ["Circle", "CCTP", "Bridge"],
  "entity": {
    "name": "Circle CCTP",
    "category": "Bridge",
    "website": "https://circle.com"
  },
  "first_seen": "2023-06-15T10:30:00Z",
  "last_seen": "2025-11-25T14:22:00Z"
}

API Fundamentals

Base URL

All API requests are made to:
https://api.range.org

Authentication

Include your API key in the X-API-KEY header with every request:
X-API-KEY: your_api_key_here

Authentication Guide

Learn more about API keys, rate limits, and security best practices

Request Format

All endpoints use GET or POST methods with:
  • Query parameters for filtering and pagination
  • JSON request bodies for complex queries (POST endpoints)
  • JSON responses for all successful requests

Response Format

All responses return JSON with consistent structure:
{
  "data": {
    /* Your requested data */
  },
  "meta": {
    "page": 1,
    "limit": 10,
    "total": 100
  }
}

Common Use Cases

Query Address Information

Get labels, entity info, and activity for any blockchain address GET /v1/address

Track Transactions

Fetch transaction history with filters for date, amount, and type GET /v1/address/transactions

Monitor Network Metrics

Access network-wide volume, active accounts, and whale movements GET /v1/network/volume

Analyze Protocols

Track DeFi protocol stats, cross-chain transfers, and bridge activity POST /v1/protocols/stats

Pagination

Many endpoints return paginated results. Control pagination with query parameters:
ParameterTypeDescriptionDefault
pageintegerPage number (1-indexed)1
limitintegerResults per page (max 100)10
Example:
curl "https://api.range.org/v1/address/transactions?address=YOUR_ADDRESS&network=solana&page=2&limit=50" \
  -H "X-API-KEY: your_api_key_here"
Response includes pagination metadata:
{
  "data": [...],
  "meta": {
    "page": 2,
    "limit": 50,
    "total": 1234,
    "pages": 25
  }
}
Some endpoints support scroll API for efficient iteration through large datasets. Check individual endpoint docs for details.

Supported Networks

Query data from 18+ blockchains with consistent API structure:
Mainnet: solanaFull support for transactions, payments, token transfers, and Solana-specific features.
Networks: cosmoshub, osmosis, celestia, dydx, neutron, injective, noble, stride, stargaze, juno, kujira, axelar IBC transfers, cross-chain messaging, and cosmos-specific transaction types.
Networks: ethereum, arbitrum, polygon, base, optimism Smart contract interactions, ERC-20 transfers, and EVM-specific data.
Stellar: stellarFull ledger and payment path data for Stellar network.
Use the network parameter to specify which blockchain to query.

Error Handling

The API uses standard HTTP status codes:
Status CodeMeaningCommon Causes
200SuccessRequest completed successfully
400Bad RequestInvalid parameters or malformed request
401UnauthorizedMissing or invalid API key
404Not FoundResource doesn’t exist
429Too Many RequestsRate limit exceeded
500Server ErrorInternal server error (rare)
Error Response Format:
{
  "statusCode": 400,
  "message": "Invalid network parameter",
  "error": "Bad Request"
}
Always check the statusCode in your error handling logic and implement retry logic with exponential backoff for 429 and 5xx errors.

Rate Limits

Monitor your usage with rate limit headers included in every response:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1732543200
PlanRate LimitMonthly Quota
Free10 req/min100 req/month
EnterpriseCustomCustom

Upgrade Your Plan

Need higher limits? Upgrade to Pro or Enterprise for production workloads.

Best Practices

Cache frequently accessed data like address labels and entity information to reduce API calls and improve performance.
Request only the data you need with appropriate limit values. For large datasets, use scroll API when available.
Implement retry logic with exponential backoff for transient errors (429, 5xx). Log all errors for debugging.
Track the X-RateLimit-Remaining header and implement throttling before hitting limits.
Coming soon! Subscribe to real-time events instead of polling for updates.

Next Steps