ReccoBeats · Rate Limits

Reccobeats Rate Limits

ReccoBeats enforces rate limits to ensure fair usage and prevent abuse, but the exact numeric thresholds are configured internally and are not published. When a client exceeds the limit, the API responds with HTTP 429 Too Many Requests and includes a Retry-After header indicating how long to wait before retrying. In addition, the audio-file analysis endpoint enforces hard input constraints: uploads are capped at 5 MB and only the first 30 seconds of audio are analyzed, with a recommended 44,100 Hz sampling rate.

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

It captures 3 rate-limit definitions, measuring requests, bytes, and seconds.

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

Tagged areas include Music, Recommendations, Audio Features, Rate Limiting, and Quotas.

3 Limits Throttle: 429
MusicRecommendationsAudio FeaturesRate LimitingQuotas

Limits

API Requests client
requests
not published
Internal rate limit; exact threshold not disclosed. Returns 429 with Retry-After when exceeded.
Audio Upload Size request
bytes
5242880
Audio-file analysis uploads are capped at 5 MB.
Audio Analysis Duration request
seconds
30
Only the first 30 seconds of an uploaded audio file are analyzed; longer audio is truncated.

Policies

Retry-After
On a 429 response, inspect the Retry-After header to determine how long to wait before the next request.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Fair Use
Rate limits exist to ensure fair usage and prevent abuse of the free, keyless API.

Sources