Update an API product and handle access changes
Check existing customer dependencies before publishing changes. Understand how unlisting, cancellation, and payment failures affect access.
On this page
Edit and publish an API or plan
- In Products, edit the document, configuration, or plans and save.
- Test the affected plan and endpoint combinations, review the preview, and publish.
- Existing buyers retain their purchased plans and configuration. Keep their origin, authentication, and endpoints available while arranging any migration with them.
Unlisting and existing access
Unlist stops new sales and removes the product from the catalog. Existing subscriptions continue under their purchased offer. Unlisting does not cancel every buyer’s subscription.
A buyer has one key per API product. Its raw value is shown only when created or rotated. If lost, the buyer can rotate it in the workspace; the previous value stops working immediately.
Manage product availabilityCancellation, failed payments, and recovery
Cancellation immediately stops new calls, then settles in-flight calls and remaining usage. It does not prorate refunds. The key record is retained.
Failed payment pauses access. Payment recovery restores access only for the current uncanceled subscription. A customer who canceled must subscribe again.
For exhausted allowances or rate limits, check remaining units and reset time first. Rotating a key does not restore an allowance.