Revelator · Rate Limits

Revelator Rate Limits

Revelator's developer documentation does not publish specific numeric API rate limits, quotas, or throttling thresholds. Access is governed by an 8-hour access token obtained from the partner login endpoints, a child-account permission model, and partner-level API keys. Practical limits are expected to be governed by subscription tier and partner agreement. No per-endpoint RPM/RPS/quota values are documented; values here are not reconciled.

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

It captures 3 rate-limit definitions, measuring duration, requests, and tracks.

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

Tagged areas include Music, Distribution, Rights, Royalties, and Payments.

3 Limits Throttle: 429
MusicDistributionRightsRoyaltiesPaymentsAnalyticsRate LimitingQuotasThrottling

Limits

Access Token Lifetime account
duration
8 hours
Access tokens obtained from /partner/account/login are valid for 8 hours and must be refreshed thereafter.
API Rate Limit account
requests
see provider documentation
No numeric per-endpoint or per-account request rate limit is published; governed by partner agreement and tier.
Ingestion Volume account
tracks
see plan
Track-ingestion batch sizes vary by subscription tier per third-party sources; not an API rate limit and not reconciled.

Policies

Token-Based Access
Most endpoints require a Bearer access token; some administrative endpoints use the partner API key directly. Keep API keys server-side.
Child-Account Model
Access scope and permitted operations are governed by the child-account permission model; some operations (e.g. contract changes) require a parent account token.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources