Spreaker · Rate Limits

Spreaker Rate Limits

The Spreaker API enforces rate limiting but does not publish exact numeric request-per-minute thresholds. The developer overview states that excessive requests result in temporary IP blacklisting and a 429 Too Many Requests response. Read (GET) requests are generally public and do not require authentication unless documented; all writes (PUT, POST, DELETE) require an OAuth2 Bearer token. List endpoints are paginated - the default page size is 50 items, adjustable up to 100 via the limit parameter, with a next_url property linking to the following page.

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

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

The profile also includes 3 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 ip
requests
not published
Excessive requests trigger temporary IP blacklisting and a 429 Too Many Requests response. No numeric threshold is documented.
Pagination Page Size request
items
100
Default page size is 50 items, adjustable up to 100 via the limit parameter. Responses include a next_url for the next page.
Authenticated Writes account
requests
not published
All PUT, POST, and DELETE requests require a valid OAuth2 Bearer token. No separate numeric write cap is documented.

Policies

IP Blacklisting
Spreaker temporarily blacklists client IPs that issue excessive requests, returning 429 until the block clears.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and avoid tight polling of statistics and search endpoints.
Pagination
Iterate large result sets by following the next_url property rather than requesting oversized pages.

Sources