specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Blubrry API providerId: blubrry-api-restful-api-for-podcast-publishing-statistics generated: '2026-09-06' method: searched source: >- https://blubrry.com/developer/api/ , https://blubrry.com/developer/api/oauth-2/ , https://blubrry.com/developer/api/podcaster.yaml , live response headers from https://api.blubrry.com/2/media/index.json created: '2026-05-04' modified: '2026-09-06' tags: - Podcasting - Statistics - Rate Limiting description: >- Blubrry publishes no rate limits. This file replaces a 2026-05-04 scaffold that asserted X-RateLimit-* headers, a 429 status and per-tier quotas that Blubrry does not in fact document or return. The developer portal, the OAuth 2 page and the published podcaster.yaml contract contain no mention of rate limiting, throttling, quotas or 429; the only stated runtime ceiling anywhere is the 1-hour access-token lifetime. A live unauthenticated request to https://api.blubrry.com/2/media/index.json returned HTTP 401 with no RateLimit-*, X-RateLimit-*, Retry-After or RateLimit-Policy header of any kind. An honest zero. limit_count: 0 limits: [] headers: observed: [] note: >- No rate-limit signalling headers observed on a live response (probed 2026-09-06). Response headers were content-type, content-length, date, server, cache-control plus CloudFront edge headers. responseCodes: throttled: null note: No throttling status code is documented. Documented error codes are 400, 401, 403 and 404. evidence: - url: https://blubrry.com/developer/api/ status: 200 finding: No rate limit, throttle, quota or 429 language on the developer portal. - url: https://blubrry.com/developer/api/podcaster.yaml status: 200 finding: The published OpenAPI declares no 429 response and no rate-limit headers. - url: https://api.blubrry.com/2/media/index.json status: 401 finding: Live response carries no RateLimit-*, X-RateLimit-* or Retry-After header. recommendation: >- Blubrry should publish a documented request ceiling and return RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset (RFC 9331 style) with a 429 on exhaustion. An agent integrating today cannot back off before it is cut off, because there is nothing to read.