Captivate · Rate Limits

Captivate Fm Rate Limits

Captivate does not publish numeric rate limits for its public API in the Postman documentation at docs.captivate.fm. Access is per-account and authenticated with a Bearer token obtained by exchanging a user ID and API token. The commercial constraint on an account is the plan's monthly download allowance (30,000 / 150,000 / 300,000 depending on tier), which governs how much listening traffic the hosting will serve - it is not a per-request API cap. No per-minute or per-hour request ceiling, burst limit, or 429 policy is documented as of the review date.

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

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

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

Tagged areas include Podcasting, Podcast Hosting, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PodcastingPodcast HostingRate LimitingQuotas

Limits

API Requests account
requests
not published
No numeric per-account or per-endpoint request-rate limit is documented for the Captivate API.
Monthly Download Allowance account
downloads
per plan (30000 / 150000 / 300000 per month)
Plan-level hosting/delivery quota on episode downloads, not an API request cap.
Media Upload Size request
bytes
not published
Audio upload size limits are not documented in the public API reference (modeled as unconfirmed).

Policies

Authentication Required
All endpoints except POST /authenticate/token require a valid Bearer token in the Authorization header.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 or 5xx response (recommended; not documented by Captivate).

Sources