Authentication

API Key Authentication

All Range Data API requests require authentication using an API key passed in the request header.

Getting Your API Key

If you need access, request a time-limited Sandbox.

Generate API Key

Navigate to your dashboard and generate a new API key

Copy & Secure

Copy your API key and store it securely. Treat it like a password, never commit it to version control.

Making Authenticated Requests

Include your API key in the Authorization header with every request:

curl -X GET "https://api.range.org/v1/address?address=YOUR_ADDRESS&network=solana" \
  -H "Authorization: Bearer YOUR_API_KEY"

const response = await fetch(
  "https://api.range.org/v1/address?address=YOUR_ADDRESS&network=solana",
  {
    headers: {
      Authorization: "Bearer YOUR_API_KEY",
    },
  }
);
const data = await response.json();

import requests

headers = {
    'Authorization': 'Bearer YOUR_API_KEY'
}

response = requests.get(
    'https://api.range.org/v1/address',
    params={'address': 'YOUR_ADDRESS', 'network': 'solana'},
    headers=headers
)
data = response.json()

const response = await fetch(
  "https://api.range.org/v1/address?address=YOUR_ADDRESS&network=solana",
  {
    headers: {
      Authorization: "Bearer YOUR_API_KEY",
    },
  }
);
const data = await response.json();

Rate Limits

Rate limits and quotas depend on your account. Data API responses do not include rate-limit headers, such as X-RateLimit-Limit, X-RateLimit-Remaining, or X-RateLimit-Reset, and do not report how many credits you have left. To check your API credits, call GET /v1/workspace/usage in the Platform API with your API key. It returns credits_used, credits_limit, credits_remaining, and reset_date, the time the credit counter resets, for the current billing period. It reports credits, not your request rate.

Error Responses

401 Unauthorized

Missing or invalid API key:

{
  "statusCode": 401,
  "message": "Unauthorized",
  "error": "Invalid or missing API key"
}

Solution: Verify your API key is correct and included in the Authorization header.

429 Too Many Requests

The request was rate limited. Solution: Back off and retry with an increasing delay rather than relying on a Retry-After header. If you hit the limit regularly, contact Range to discuss higher limits.

Best Practices

Environment Variables

Store your API key in environment variables, never hardcode it:

export RANGE_API_KEY="YOUR_API_KEY"

const apiKey = process.env.RANGE_API_KEY;

Server-Side Only

Never expose your API key in client-side code (frontend JavaScript, mobile apps). Make API calls from your backend server.

Key Rotation

Rotate your API keys periodically and immediately if you suspect they’ve been compromised. You can generate new keys in your dashboard.

Monitor Usage

Track your API usage in the Range dashboard to avoid hitting rate limits and optimize your integration.

Overview

API Reference

API Key Authentication

Getting Your API Key

Making Authenticated Requests

Rate Limits

Error Responses

401 Unauthorized

429 Too Many Requests

Best Practices

Need Help?

Discuss Rate Limits

Contact Support

​API Key Authentication

​Getting Your API Key

​Making Authenticated Requests

​Rate Limits

​Error Responses

​401 Unauthorized

​429 Too Many Requests

​Best Practices

​Need Help?

Discuss Rate Limits

Contact Support

API Key Authentication

Getting Your API Key

Making Authenticated Requests

Rate Limits

Error Responses

401 Unauthorized

429 Too Many Requests

Best Practices

Need Help?