Transistor · Rate Limits

Transistor Rate Limits

Transistor publishes a single, explicit API rate limit: 10 requests per 10 seconds. Exceeding the limit returns an HTTP 429 error and blocks API access for 10 seconds. Transistor also advises against using the API as a primary live data source for website content, recommending caching of API responses instead. Separate from API request limits, each subscription plan caps monthly podcast downloads and the number of private podcast subscribers.

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

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

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

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

3 Limits Throttle: 429
PodcastingPodcast HostingAPIRate LimitingQuotas

Limits

API Requests account
requests
10 per 10 seconds
Exceeding this returns HTTP 429 and blocks access for 10 seconds.
Monthly Downloads account
downloads
per plan (20K Starter, 100K Professional, 250K Business, custom Enterprise)
Download allowance is a billing quota set by the subscription plan, not an API request limit.
Private Subscribers account
subscribers
per plan (50 Starter, 500 Professional, 3000 Business, custom Enterprise)
Private podcast subscriber cap set by the subscription plan.

Policies

Throttle Window
Requests are counted in a rolling 10-second window; more than 10 in that window trips the limit.
Cooldown
After a 429, API access is blocked for 10 seconds before requests are accepted again.
Caching Guidance
Transistor recommends caching API responses and not using the API as a live data source for website content.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor the cooldown after a 429 response.

Sources