# Meter Usage Analytics adds support for filtering multiple tenants and dimension values ## What’s new Updates the [tenant_filters](https://docs.stripe.com/api/billing/analytics/meter-usage/retrieves.md?api-version=2025-11-17.preview#retrieves_billing_analytics_meter_usage-meters-tenant_filters) and [dimension_filters](https://docs.stripe.com/api/billing/analytics/meter-usage/retrieves.md?api-version=2025-11-17.preview#retrieves_billing_analytics_meter_usage-meters-dimension_filters) parameters in the [Meter Usage Analytics API](https://docs.stripe.com/api/billing/meter_usage.md?api-version=2025-11-17.preview) to accept an array of strings instead of a single string value. This change allows you to filter meter usage data across multiple tenants or dimension values in a single API call. Previously, each filter parameter accepted only a single string value, requiring multiple API calls to retrieve usage data for different tenant or dimension combinations. ## Why is this a breaking change? Existing integrations that pass single string values receive validation errors until they’re updated to use the array format. This breaking change enables more flexible filtering capabilities that support querying usage data across multiple values simultaneously, reducing the number of API calls needed for complex usage reporting scenarios. ## Impact You must update your integration to pass arrays of strings for the `tenant_filters` and `dimension_filters` parameters when [retrieving meter usage analytics](https://docs.stripe.com/api/billing/meter_usage/create.md?api-version=2025-11-17.preview). If your integration currently passes single string values, you need to wrap them in arrays. ## Changes #### REST API | Field | Change | From → to | | ------------------------------------------------------------------ | ------- | -------------------------------------------------- | | `Billing.Analytics.MeterUsage#retrieve.meters[].dimension_filters` | Changed | `string → array(string)`, `string → array(string)` | #### Ruby | Field | Change | From → to | | ----------------------------------------------------------------------- | ------- | -------------------------------------------------- | | `Billing::Analytics::MeterUsageRetrieveParams::Meter.dimension_filters` | Changed | `string → array(string)`, `string → array(string)` | #### Python | Field | Change | From → to | | ------------------------------------------------------------------- | ------- | -------------------------------------------------- | | `billing.analytics.MeterUsageRetrieveParamsMeter.dimension_filters` | Changed | `string → array(string)`, `string → array(string)` | #### PHP | Field | Change | From → to | | ------------------------------------------------------------------------- | ------- | -------------------------------------------------- | | `Billing\Analytics\MeterUsage.retrieve().$params.meter.dimension_filters` | Changed | `string → array(string)`, `string → array(string)` | #### Java | Field | Change | From → to | | ---------------------------------------------------------------------- | ------- | -------------------------------------------------- | | `billing.analytics.MeterUsageRetrieveParams.meters[].dimensionFilters` | Changed | `string → array(string)`, `string → array(string)` | #### Node.js | Field | Change | From → to | | ----------------------------------------------------------------------- | ------- | -------------------------------------------------- | | `Billing.Analytics.MeterUsageRetrieveParams.meters[].dimension_filters` | Changed | `string → array(string)`, `string → array(string)` | #### Go | Field | Change | From → to | | -------------------------------------------------------- | ------- | -------------------------------------------------- | | `BillingAnalyticsMeterUsageMeterParams.DimensionFilters` | Changed | `string → array(string)`, `string → array(string)` | #### .NET | Field | Change | From → to | | --------------------------------------------------------- | ------- | -------------------------------------------------- | | `BillingAnalyticsMeterUsageMeterOptions.DimensionFilters` | Changed | `string → array(string)`, `string → array(string)` | ## Upgrade #### REST API 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. If you use an SDK, upgrade to the corresponding SDK version for this API version. - If you don’t use an SDK, update your [API requests](https://docs.stripe.com/api/versioning.md) to include `Stripe-Version: 2025-11-17.preview` 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Ruby 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Ruby SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Python 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Python SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### PHP 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your PHP SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Java 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Java SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Node.js 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Node SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### Go 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your Go SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md). #### .NET 1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench. 1. Upgrade your .NET SDK to the latest version. 1. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md). 1. [Test your integration](https://docs.stripe.com/testing.md) against the new version. 1. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md). 1. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours. Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).