Amberdata · Rate Limits

Amberdata Rate Limits

Amberdata enforces per-account rate limits on REST API requests, scoped to the user-specific x-api-key. Limits and historical-depth entitlements vary by subscription plan and contract. Specific per-plan request-rate values are not publicly published and are not reconciled in this artifact. WebSocket streaming connections are subscription-based rather than per-request metered.

Amberdata Rate Limits is the machine-readable rate-limit profile for Amberdata on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, history, and connections.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Crypto, Blockchain, Market Data, Digital Assets, and Rate Limiting.

3 Limits Throttle: 429
CryptoBlockchainMarket DataDigital AssetsRate LimitingQuotasThrottling

Limits

REST Requests account
requests
see provider documentation
Per-account REST request rate, scoped to the x-api-key; varies by plan.
Historical Data Depth account
history
see provider documentation
Available historical lookback varies by subscription entitlement.
WebSocket Subscriptions account
connections
see provider documentation
Real-time streaming is subscription-based; concurrent connection and topic limits vary by plan.

Policies

API Key Scoping
All REST requests require the unique user-specific x-api-key header; limits are enforced per account.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources