Scheduled
Changes to estimated_total for list operations
For large datasets, estimated_total in paginated responses for list operations returns a capped value instead of an exact count.
What's new?
We're introducing a cap on estimated_total in the meta.pagination object returned by list operations. For datasets with more than 100,000 matching entities, estimated_total returns 100001 instead of an exact count.
This update is scheduled for May 18, 2026.
How it works
The meta.pagination object in responses from list operations includes the estimated_total field. It gives you an idea of how many entities match your query, so you know roughly how many pages of results to expect.
For datasets with 100,000 or fewer results, estimated_total continues to return the exact count. There's no change from current behavior.
For datasets with more than 100,000 results, estimated_total returns 100001 to indicate more than 100,000 matching entities. estimated_total may also return -1 if counting is skipped, or the count couldn't be calculated.
| Context | estimated_total value |
|---|---|
| Less than 100,000 results | Exact count |
| More than 100,000 results | 100001 |
| Counting is skipped | -1 |
| Count couldn't be calculated | -1 |
This change affects all list operations across the Paddle API, including list transactions, list customers, list subscriptions, list products, list prices, list discounts, and list adjustments.
Update your integration
If your integration uses estimated_total to calculate total pages, display record counts, or make decisions, you should update it to handle the new return values.
We recommend using has_more and next, rather than relying on estimated_total for exact counts. The has_more field tells you whether there are more results, and next gives you the URL to fetch the next page. Use these to iterate through all pages of results.
See Pagination for more information.
Summary of changes
Changes to the pagination response
This change updates the behavior of the estimated_total field in the meta.pagination object. It doesn't introduce new fields or endpoints.
estimated_total | For datasets with more than 100,000 results, returns 100001 instead of an exact count. Returns -1 if the count is unavailable. |
Next steps
This change is scheduled for May 18, 2026 and applies to both sandbox and production accounts.
You may need to update your integration as a result of this update.
Relying on
estimated_totalfor an exact countUpdate your code to handle the value
100001(meaning more than 100,000 results) and-1(counting is skipped, or the count couldn't be calculated).Using
has_moreandnextto page through resultsNo changes are needed.
If you need exact counts for large datasets, contact the Paddle support team to discuss options.