Megaphone · Rate Limits

Megaphone Rate Limits

The Megaphone API is rate limited to 60 requests per minute (1 request per second) per API token, as stated in Megaphone's API documentation. List endpoints are paginated with an RFC 5988 Link header (rel="next") plus page and per_page query parameters, so large data pulls should page sequentially while staying under the per-second cap. Bulk data is better retrieved through the pull-based Metrics Export Service and Impressions Export Service than by paging the standard endpoints.

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

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

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

Tagged areas include Podcasting, Advertising, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PodcastingAdvertisingRate LimitingQuotas

Limits

API Requests token
requests
60 per minute (1 per second)
Documented per-token request rate limit across the Megaphone REST API.
Pagination endpoint
items
page / per_page via Link header
List endpoints return an RFC 5988 Link header with rel="next"; page sequentially.
Bulk Export account
records
use export services
Metrics Export Service and Impressions Export Service are the intended path for large data volumes.

Policies

Backoff Strategy
On a 429 response, back off and retry - stay within 1 request per second and implement exponential backoff with jitter.
Token Scope
Tokens are per-user and carry the generating user's role; do not reuse a token across organizations.
Pagination Discipline
Follow the Link header rel="next" relation rather than guessing page counts, and prefer export services for bulk pulls.

Sources