- Breaking changes
- Public preview
Removes the rate limit parameter from the Batch Job v2 object Breaking changes Public preview
What’s new
Removes the maximum_rps parameter from the Batch Job v2 object and the create Batch Job v2 endpoint. Previously, you could use maximum_rps to set a per-second request rate limit when creating a batch job. We now manage batch job throughput automatically.
Why is this a breaking change?
If your integration passes maximum_rps when creating a Batch Job v2, you must remove that parameter from your request. Requests that include maximum_rps return an error after this change takes effect.
Impact
You no longer need to configure a rate limit when creating a Batch Job v2. We now manage throughput automatically, giving you consistent performance without any per-request configuration. Before upgrading to this API version, remove maximum_rps from any create Batch Job v2 requests.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| maximum_rps | Removed | V2. Core. BatchJob V2. Core. BatchJob#create |
Upgrade
- View your current API version in Workbench.
- 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 to include Stripe-Version: 2026-06-24. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.