Cloudinary API
access_mode body parameter removal on POST /v1_1/{id}/{id}/upload
Deprecated, no dateSubscribe to Cloudinary APIShare
The body parameter access_mode on POST /v1_1/{id}/{id}/upload is deprecated without a shutdown date and is no longer supported. Calls using this parameter fail. Developers using this endpoint should update their request payloads accordingly.
Calls it hits
POST /v1_1/{id}/{id}/uploadbody parameter access_mode
What to use instead of these calls
Send access_control, specified as an array of access types such as token or anonymous with start and end dates, instead of access_mode.
In Cloudinary API's words
Note : The access_mode parameter is no longer supported. To restrict access to assets, you can use the access_control parameter.
Facts
- API
- Cloudinary API
api.cloudinary.com - Kind
- Parameter 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}/{id}/upload, body parameter 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}/resources/{id}/upload/update_access_modeEndpoint 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.