Seconding this. We also need the same questions answered.
Original Message:
Sent: 02-18-2026 13:20
From: Alex Sander Felicio
Subject: Updates: Partner Billing Usage API is now ready to consume
We currently use the Partner Billing Usage API (/api/v2/billing/trusteebillingoverview/{trustorOrgId}) for usage monitoring and invoice generation, so we're planning the cutover to the new Billing APIs.
A few questions to help us prepare and test properly:
Endpoint mapping / parity: Is there a recommended mapping from trusteebillingoverview to the new endpoints (usage, invoices, subscriptions, contracts), or a "migration guide" showing what replaces what?
Auth & permissions: Will the new APIs require any new OAuth scopes/roles compared to the current Partner Billing Usage API?
Data availability timeline: When do you expect non-mock (real) data to be available in preview/sandbox for partner testing?
Deprecation details: Will there be a formal deprecation notice with a fixed date and a minimum overlap window (e.g., X days) where both APIs remain available in production?
Rate limits & pagination: Any changes in rate limits, pagination patterns, or billing period boundaries we should account for?
Invoices source of truth: For invoice generation, should we rely on "invoice endpoints" as the source of truth, or is "usage/rate plan" data still expected to be used to compute charges externally?
We'll start integrating against the preview API now and will share feedback/issues as we test. Thanks!
------------------------------
Alex Sander Felicio
Original Message:
Sent: 09-08-2025 10:33
From: Developer Community
Subject: Updates: Partner Billing Usage API is now ready to consume
Summary
Genesys Cloud is transitioning to a new billing system, and as a result, the Partner Billing Usage API will be replaced. We are taking this opportunity to future-proof the API for a better customer experience.
You are impacted if this use case applies to you:
- You are a Genesys Cloud partner using the Partner Billing Usage API to monitor customer usage and generate invoices based on the API data.
- Partner Billing Usage API: /api/v2/billing/trusteebillingoverview/{trustorOrgId}
The API is now available to begin your development work. Please note, only mock data will be available at this time. Genesys plans to deprecate the Partner Billing Usage API at a later date after satisfactory testing and deployment of the new billing system. https://developer.genesys.cloud/platform/preview-apis#billing
We will stay in touch with you throughout the next few months, explaining new milestones and calls to action as necessary for you to complete your testing.
Effective Date
As notified by Genesys; between May – July 2026.
Details
The Partner Billing Usage API is intended for Genesys Partner companies to create systems for customer billing of Genesys Cloud users, devices and resources, and AppFoundry applications. The replacement of the Billing System requires us to replace the API.
The new API has a much richer data set for consumers to see their contracts, subscriptions, rate plans, invoices, quantity commits, balances, drawdown units and overages by billing period all in the same API.
Customer Impact
Customers and Partners consuming the Partner Billing Usage API will need to cut-over to the new API endpoints. Timelines will be communicated along the way to keep all partners informed of the change.
Impacted Resources
Partner Billing Usage API:
Issue References
[PURE-6749]
Contacts
@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.