Removes legacy usage-based billing
We’ve removed support for legacy usage-based billing. You can no longer create a price with a usage_type of metered without a specified meter. We’ve also removed the billing_thresholds from the subscription endpoints. - Removed billing_thresholds from Subscription endpoints. - Removed aggregate_usage from Price endpoints. - Using usage_type of metered without a specified meter now returns an error on Price creation. - Removed support for attaching prices of usage_type=metered without a set meter to Subscriptions, Subscription Schedules and Quotes.
docs.stripe.comquote checked- parameter change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Removes legacy usage-based billing](https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-legacy-usage-based-billing.md) | Billing, Invoicing | Breaking | api |
Also readmatches the page ✓
- Removed `billing_thresholds` from [Subscription](https://docs.stripe.com/api/subscriptions/object.md?api-version=2025-03-31.basil) endpoints. - Removed `aggregate_usage` from [Price](https://docs.stripe.com/api/prices/object.md?api-version=2025-03-31.basil) endpoints. - Using `usage_type` of `metered` without a specified `meter` now returns an error on [Price](https://docs.stripe.com/api/prices/object.md?api-version=2025-03-31.basil) creation. - Removed support for attaching prices of `usage_type=metered` without a set `meter` to Subscriptions, Subscription Schedules and Quotes.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?