Rolling out
Pagination added to list operations
Available now, but scheduled to be enforced on March 11, 2025
Action needed by March 11, 2025You might need to make changes to your integration as a result of this update. We've reached out directly to Paddle platform users who are impacted with next steps.
What's new?
We've updated core list operations in the Paddle Classic API so that responses are now paginated, making it easier to work with a large number of records.
Pagination parameters and keys are available now, but page limits aren't enforced. They're scheduled to be enforced on March 11, 2025.
How does it work?
List operations let you work with a number of records at once. Previously, most list operations weren't paginated, which meant all records were returned.
To improve performance for Paddle users who have a large number of records, we've added pagination to core list operations in the Paddle Classic API. This lets you get data from the API in smaller, manageable batches, reducing the likelihood of timeouts or excessive memory consumption in your integration.
Most operations now return between 250 and 500 results per page. You can page through results for a response using the pagination parameters for the endpoint that you're working with. Most operations return count and total keys, so you can determine how many records per page and in total.
Summary of changes
| Parameters | Response | Default | Max | |
|---|---|---|---|---|
| List products | Added limit and offset. | Added response.count and response.total. | 250 | 250 |
| List coupons | Added limit, offset, and is_valid. | Added count and total. | 500 | 500 |
| List plans | Added limit and offset. | Added count and total. | 500 | 500 |
| List payments | Added limit and offset. | Added count and total. | 500 | 500 |
| List modifiers | No change. Use after and results_per_page. | Added count and total. | 250 | 250 |
| List transactions | No change. Use page and results_per_page. | No change. | 15 | 300 |
| List users | No change. Use page and results_per_page. | No change. | 250 | 250 |
| Get webhook history | No change. Use page and alerts_per_page. | No change. | 250 | 250 |
Next steps
You might need to make changes to your integration as a result of this update. Check the docs for the operations that you use in your integration to learn how pagination works and update.
We've reached out directly to Paddle platform users who exceed the new maximum limits with information about which operations are impacted and what you need to do next.
This change only impacts the Paddle Classic API. It doesn't impact Paddle Billing.