Stripe Batch Jobs v2 supports DELETE operations
Introduced 2026-04-22 · score 0.99
HOW TO USE IT
When batching resource deletions, create a Batch Job with `endpoint.http_method` set to `delete`. Include the `2026-04-22.preview` Stripe API version in the request.
curl -X POST https://api.stripe.com/v2/core/batch_jobs \
-H "Authorization: Bearer <YOUR_SECRET_KEY>" \
-H "Stripe-Version: 2026-04-22.preview" \
--json '{"endpoint":{"path":"<RESOURCE_ENDPOINT_PATH>","http_method":"delete"},"metadata":{},"skip_validation":false}'"endpoint": {"path": "/v1/subscriptions/:subscription/migrate", "http_method": "delete"}WHY THIS HELPS
Batch DELETE operations on Stripe resources, such as canceling multiple subscriptions.
BEFORE THIS CHANGE
Set `endpoint.http_method` to `post`; this parameter previously only supported `post`.
REQUIREMENTS AND LIMITATIONS
- Availability: preview
- endpoint (required): Object configuring the batch job endpoint.
- endpoint.path (required): Path for the endpoint; use the resource endpoint path to batch.
- endpoint.http_method (required): HTTP method for the operation; the release note documents `delete` and `post` as allowed values.
- metadata (required): Metadata of the batch job; use an empty object when no metadata is supplied.
- skip_validation (required): Whether validation runs before executing the batch job.
- Prerequisite: For REST API requests, include the `Stripe-Version: 2026-04-22.preview` header. Use a Stripe secret key as the bearer credential.
- The `endpoint.http_method` parameter previously only supported `POST` operations.
- The change does not affect existing batch operations that use the `POST` method.
FIRST-PARTY EVIDENCE
- https://docs.stripe.com/changelog/dahlia/2026-04-22/batch-api-delete-method
- https://docs.stripe.com/api/v2/core/batch-jobs/create?api-version=2026-04-22.preview
Check the installed version and the source before using it. Entry JSON