You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Getting an error 400 when using a third party app
I am currently using an app to record lectures and then I upload them to my drop box. This is the second semester I've done this so I know it works. This evening when I was trying to upload the recordings I kept getting Dropbox.com error 400. What does this mean? I've tried two different recordings and neither are uploading. HELP. Everything is up to date and I just did a backup this evening trying to solve the problem.
Bholcombe If you're receiving this error, it likely indicates that the third party app you're using is still using the now-retired API v1.
If you're not the developer of the app, you'll need to contact them and request an updated version of the app that uses API v2 instead. They can contact us and request an extension for access to API v1 if necessary.
Same here. A script that's been running daily for a couple of years started getting 400s (I noticed it this morning)
The script is in go, and I'm using this package https://github.com/stacktic/dropbox
Ok turns out dropbox API v1 has been turned off: https://www.dropbox.com/developers/apps/create
On September 28, 2017, API v1 will be turned off, so it's time to move to API v2.
If you want your app's Dropbox integration to keep working, upgrade to API v2.
For details about the deprecation, check out the blog post.
Please acknowledge that API v1 is being deprecated by clicking the box below. If you do not acknowledge that you're aware of the deprecation, your app's users will be notified as part of the deprecation timeline.
I understand that API v1 is being deprecatedAs a note: I've tried using the unofficial-official go package and I'm getting the same error...
https://github.com/dropbox/dropbox-sdk-go-unofficial
linked from
- Greg-DB
Dropbox Staff
Bholcombe If you're receiving this error, it likely indicates that the third party app you're using is still using the now-retired API v1.
If you're not the developer of the app, you'll need to contact them and request an updated version of the app that uses API v2 instead. They can contact us and request an extension for access to API v1 if necessary.
