GET /v2/images/collections/featured* → endpoint removal
Shutterstock API
Stopped working
On February 14, 2025, Shutterstock removed the GET /v2/images/collections/featured* endpoints due to service deprecation. Calls to these featured collections routes now fail.
Calls it hits
GET /v2/images/collections/featured*
What to use instead of these calls
Remove the deprecated calls, as featured collections have no direct replacement. What to display instead requires a product decision, though you can maintain your own curated sets using the catalog collections endpoints at GET /v2/catalog/collections.
Shutterstock retired featured collections with no replacement, so what to show instead is a product decision.
In Shutterstock API's words
Removed the following unused endpoints due to service deprecation: - GET /v2/images/collections/featured - GET /v2/images/collections/featured/{id} - GET /v2/images/collections/featured/{id}/items - GET /v2/videos/collections/featured - GET /v2/videos/collections/featured/{id} - GET /v2/videos/collections/featured/{id}/items
Facts
- API
- Shutterstock API
api.shutterstock.com - Kind
- Endpoint removal
- Announced
- February 14, 2025
- Takes effect
- February 14, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Shutterstock API's own pages
Questions
When does this change take effect?
Calls to GET /v2/images/collections/featured* on Shutterstock API stopped working on February 14, 2025.
What happens to calls after February 14, 2025?
They have failed since February 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 Shutterstock API 1
-
GET /v2/videos/collections/featured*Endpoint 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.