Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Solved
Did 404 change to 409 in v2?
I'm migrating Nebulous Notes to v2, and I noticed that if I sync a file that doesn't exist on DB, I get a 409, instead of 404. Is this intentional? I use the status check in my logic to determine whether or not to upload a file, and want to make sure I set it to the right code.
- Yes, API v2 makes different use of status codes than API v1. For example, where API v1 may have used a 404 to indicate a non-existent file (among other issues), that would be a 409 error in API v2, with more specific error information available in the body.
You can find information on the design of API v2 on the blog:
https://blogs.dropbox.com/developers/2015/04/a-preview-of-the-new-dropbox-api-v2/
https://blogs.dropbox.com/developers/2015/04/how-many-http-status-codes-should-your-api-use/
You can find more information on error handling in the API v2 documentation:
https://www.dropbox.com/developers/documentation/http/documentation#error-handling
Hope this helps!
1 Reply
- Greg-DB
Dropbox Community Moderator
Yes, API v2 makes different use of status codes than API v1. For example, where API v1 may have used a 404 to indicate a non-existent file (among other issues), that would be a 409 error in API v2, with more specific error information available in the body.
You can find information on the design of API v2 on the blog:
https://blogs.dropbox.com/developers/2015/04/a-preview-of-the-new-dropbox-api-v2/
https://blogs.dropbox.com/developers/2015/04/how-many-http-status-codes-should-your-api-use/
You can find more information on error handling in the API v2 documentation:
https://www.dropbox.com/developers/documentation/http/documentation#error-handling
Hope this helps!
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
