DatoCMS Content Management API
DELETE /uploads/batch-destroy endpoint removal
Stopped workingSubscribe to DatoCMS Content Management APIShare
Calls to DELETE /uploads/batch-destroy on DatoCMS Content Management API stopped working on May 14, 2025.
Calls it hits
DELETE /uploads/batch-destroy
What to use instead of these calls
Use POST /uploads/bulk/destroy (bulk_destroy) instead.
In DatoCMS Content Management API's words
Starting May 14th, 2025, our legacy uploads batch operation endpoints — which have been deprecated for years — will be discontinued and will return error responses.
Facts
- API
- DatoCMS Content Management API
site-api.datocms.com - Kind
- Endpoint removal
- Announced
- April 14, 2025
- Takes effect
- May 14, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against DatoCMS Content Management API's own pages
Questions
When does this change take effect?
Calls to DELETE /uploads/batch-destroy on DatoCMS Content Management API stopped working on May 14, 2025.
What happens to calls after May 14, 2025?
They have failed since May 14, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from DatoCMS Content Management API 4
-
DELETE /itemsEndpoint removal Stopped working -
PUT /items/publishEndpoint removal Stopped working -
PUT /items/unpublishEndpoint removal Stopped working -
PUT /uploads/batch-add-tagsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.