Cloudinary API
POST /v1_1/{id}/resources/{id}/upload/update_access_mode endpoint removal
Deprecated, no dateSubscribe to Cloudinary APIShare
The endpoint POST /v1_1/{id}/resources/{id}/upload/update_access_mode has been deprecated without a shutdown date. Calls to this endpoint are used to update asset access modes by public ID, tag, or prefix. Following its removal, these calls will fail.
Calls it hits
POST /v1_1/{id}/resources/{id}/upload/update_access_mode
What to use instead of these calls
Restrict access using access_control instead. Set it per asset through the Upload API explicit method or the Admin API update resource method at POST /v1_1/{cloud_name}/resources/{resource_type}/{type}/{public_id}.
In Cloudinary API's words
Updates the access mode of resources (assets) by public ID, by tag, or by prefix. Deprecated.
Facts
- API
- Cloudinary API
api.cloudinary.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Cloudinary API's own pages
Questions
When does this change take effect?
Cloudinary API deprecated POST /v1_1/{id}/resources/{id}/upload/update_access_mode without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Cloudinary API has not given a shutdown date yet.
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 Cloudinary API 4
-
No date
POST /v1_1/{id}/{id}/uploadParameter removal Deprecated, no date -
No date
POST /v1_1/{id}/{id}/uploadParameter removal Deprecated, no date -
No date
POST /v1_1/{id}/{id}/uploadParameter removal Deprecated, no date -
No date
POST /v1_1/{id}/{id}/uploadParameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.