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, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

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/paddle-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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