Buzzsprout · Rate Limits

Buzzsprout Rate Limits

Buzzsprout does not publish fixed numeric per-minute or per-hour rate limits for its REST API. The documentation instead emphasizes correct client behavior: send a custom User-Agent (default agents may be blocked), set Content-Type to application/json; charset=utf-8 on writes (a wrong type returns 415), and honor HTTP caching. Responses include ETag / Last-Modified headers, and clients are expected to store them and resubmit as If-None-Match / If-Modified-Since to get 304 Not Modified responses and avoid unnecessary traffic. The practical usage ceiling is the account's plan upload-hour allowance rather than an API request cap.

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

It captures 2 rate-limit definitions, measuring requests and hours.

The profile also includes 4 backoff/retry policies defined and response codes documented for unsupportedMediaType and serverErrors.

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

2 Limits
PodcastingPodcast HostingAudioRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Buzzsprout API.
Upload Hours account
hours
per plan
Audio upload volume is bounded by the account's plan allowance, not by an API request cap.

Policies

User-Agent Required
Requests must set a custom User-Agent header; some default agents are blocked.
HTTP Caching
Responses carry ETag / Last-Modified; clients should send If-None-Match / If-Modified-Since to receive 304 Not Modified.
Content-Type Enforcement
POST and PUT requests must use Content-Type application/json; charset=utf-8 or the API returns 415 Unsupported Media Type.
Retry on Server Errors
Clients should implement retry logic for 5xx responses (500, 502, 503, 504), ideally with exponential backoff.

Sources