Podbean · Rate Limits

Podbean Rate Limits

Podbean does not publish fixed numeric rate limits for its public API. Access is gated first by OAuth 2.0 - an app must be registered and hold a valid access token scoped to a podcast (single-podcast via Client Credentials or Authorization Code, or per-podcast via the Multiple Podcasts token flow). Practical throughput is shaped by the account's hosting plan (storage, bandwidth, and monthly upload allowances) rather than by a documented per-minute request cap. Media bytes are not sent through the API - the file upload flow returns a presigned URL that the client PUTs to directly - so large uploads do not consume API request budget.

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

It captures 4 rate-limit definitions, measuring requests, podcasts, and bytes.

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

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

4 Limits Throttle: 429
PodcastingPodcast HostingRate LimitingQuotas

Limits

API Requests app
requests
not published
No fixed numeric request-rate limit is documented for the public API.
OAuth Token Scope token
podcasts
per token
An access token is bound to a single podcast; agencies use Multiple Podcasts tokens for per-podcast access.
Upload Allowance account
bytes
per plan (monthly upload allowance)
Media upload volume is governed by the hosting plan (e.g., 1GB/mo on Unlimited Audio, up to 40GB/mo on higher tiers).
Bandwidth account
bytes
per plan (unmetered on most paid tiers)
Playback bandwidth is a hosting-plan attribute, not an API request limit.

Policies

OAuth 2.0 Gating
All non-oEmbed endpoints require a valid OAuth 2.0 access token obtained from a registered app.
Presigned Uploads
Media bytes bypass the API request path via a presigned URL PUT, so large files do not consume API request budget.
Backoff Strategy
Clients should refresh on 401 and apply exponential backoff with jitter on 429 or 5xx responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/podbean-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.