Dropbox Content API
POST /2/files/upload_session/append endpoint removal
Deprecated, no dateSubscribe to Dropbox Content APIShare
The POST /2/files/upload_session/append endpoint has been deprecated without a shutdown date. Calls made to this route will eventually fail. The route is deprecated in favor of upload_session/append:2.
Calls it hits
POST /2/files/upload_session/append
What to use instead of these calls
Call POST /2/files/upload_session/append_v2 instead. Note that the replacement endpoint takes a cursor and a close flag.
In Dropbox Content API's words
route upload_session/append (UploadSessionCursor, Void, UploadSessionLookupError) deprecated by upload_session/append:2
Facts
- API
- Dropbox Content API
content.dropboxapi.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Dropbox Content API's own pages
Questions
When does this change take effect?
Dropbox Content API deprecated POST /2/files/upload_session/append without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Dropbox Content 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.