Cloudinary API
callback body parameter removal on POST /v1_1/{id}/{id}/upload
Deprecated, no dateSubscribe to Cloudinary APIShare
The body parameter callback on the POST /v1_1/{id}/{id}/upload endpoint is deprecated without a shutdown date. This parameter previously served as a URL to redirect to after upload completion instead of returning the upload response. When support is fully removed, requests relying on this parameter will fail.
Calls it hits
POST /v1_1/{id}/{id}/uploadbody parameter callback
What to use instead of these calls
Read the upload response directly, or pass notification_url to receive the upload result as a webhook.
In Cloudinary API's words
A URL to redirect to after the upload is completed instead of returning the upload response.
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 callback 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.