Paddle · Rate Limits

Paddle Rate Limits

The Paddle API enforces per-IP-address rate limits. Most endpoints allow up to 240 requests per minute. Pricing-preview endpoints (preview transaction and preview prices) allow a higher 1,000 requests per minute. Subscription immediate (one-time) charges are additionally constrained per subscription to 20 chargeable updates per hour and 100 per 24-hour period. When a limit is exceeded Paddle returns HTTP 429 with a Retry-After header indicating how long to wait before retrying.

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

It captures 4 rate-limit definitions, measuring requests.

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

Tagged areas include Billing, Payments, Subscriptions, Merchant of Record, and SaaS.

4 Limits Throttle: 429
BillingPaymentsSubscriptionsMerchant of RecordSaaSRate LimitingQuotasThrottling

Limits

Standard Requests Per Minute ip
requests
240
Up to 240 requests per minute per IP address across most API operations.
Pricing Preview Requests Per Minute ip
requests
1000
Up to 1,000 requests per minute per IP address for preview transaction and preview prices endpoints.
Subscription Immediate Charges (Hourly) subscription
requests
20
Up to 20 chargeable subscription updates per hour, per subscription.
Subscription Immediate Charges (Daily) subscription
requests
100
Up to 100 chargeable subscription updates per 24-hour period, per subscription.

Policies

Retry-After
429 responses include a Retry-After header indicating how long to wait; further requests are blocked for 60 seconds after exceeding the standard limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor the Retry-After header.

Sources