Removes legacy usage-based billingBreaking changes
What’s new
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.
We’ve removed billing_thresholds and aggregate_usage from all API endpoints. You can no longer create legacy usage-based prices or attach existing legacy usage-based prices to quotes, upcoming invoices, or subscriptions.
A legacy usage-based price is defined as a price with a usage_type of metered without a specified meter.
Why is this a breaking change?
- Removed
billing_from Subscription endpoints.thresholds - Removed
aggregate_from Price endpoints.usage - Using
usage_oftype meteredwithout a specifiedmeternow returns an error on Price creation. - Removed support for attaching prices of
usage_without a settype=metered meterto Subscriptions, Subscription Schedules and Quotes.
Impact
Follow our migration guide to update your integration to use meters.