Summary
The maximum supported value for the pageSize query parameter on the Billing Contracts API is being reduced from 200 to 10 entities per request.
Following this change, requests specifying a pageSize greater than 10 will no longer be accepted as requested.
Customers, partners, and integrations that currently retrieve more than 10 contracts per request should update their implementations to use pagination and retrieve additional pages as needed.
Effective Date
Friday, September 4, 2026
Additional Resources
The Billing Contracts API currently supports retrieving up to 200 entities in a single request.
To support continued platform growth and provide a more consistent API experience, the maximum page size is being reduced to optimize paginated resource retrieval and align the API with current platform best practices.
The reduced maximum page size provides:
- More consistent and predictable API response times.
- Improved responsiveness when retrieving larger data sets.
- More efficient resource utilization.
- Consistent adoption of cursor-based pagination.
- Improved scalability as API usage continues to grow.
Customer Impact
Customers, partners, and integrations that currently request more than 10 Billing Contracts in a single API call are impacted.
Integrations should update the pageSize value to a maximum of 10 and use the API's pagination mechanism to retrieve additional results.
Requests that already specify a pageSize of 10 or fewer are not affected.
Customer Action Required
Customers and partners using the Billing Contracts API should:
- Review integrations that explicitly set the pageSize query parameter.
- Update any pageSize value greater than 10 to a maximum of 10.
- Ensure integrations correctly implement pagination to retrieve additional contracts.
Impacted Resources
GET /api/v2/billing/contracts
get-api-v2-billing-contracts
Issue References
PURE-6749
Contacts
@Saikamal Paradi @Isla Taylor Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.