We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Refresh Token Url
Hi All, I am using Dropbox HTTP integration and for the refresh token, we are using "https://www.dropbox.com/oauth2/token" EP. suddenly I got an error for one of our users. "Error (400) Somethi...
jaksonjohn The /oauth2/token endpoint is an OAuth endpoint, not a web page, and so should be accessed on api.dropboxapi.com, not www.dropbox.com.
While it's possible that it happened to work on that domain previously, it was never officially meant for that and was not documented as such, and so would not be officially supported on that www domain.
For reference, the official documentation does show (and has shown as far back as I'm aware) that it should be accessed on api.dropboxapi.com.
As such, apps should access that endpoint on api.dropboxapi.com, not www.dropbox.com. Any apps that were using that on www.dropbox.com, even if it happened to work for them previously, should update their code to use the correct api.dropboxapi.com instead.
i think no. the url is to be changed. i have experience in it.
Greg-DB
Dropbox Staff
Dropbox Staffjaksonjohn The /oauth2/token endpoint is an OAuth endpoint, not a web page, and so should be accessed on api.dropboxapi.com, not www.dropbox.com.
While it's possible that it happened to work on that domain previously, it was never officially meant for that and was not documented as such, and so would not be officially supported on that www domain.
For reference, the official documentation does show (and has shown as far back as I'm aware) that it should be accessed on api.dropboxapi.com.
As such, apps should access that endpoint on api.dropboxapi.com, not www.dropbox.com. Any apps that were using that on www.dropbox.com, even if it happened to work for them previously, should update their code to use the correct api.dropboxapi.com instead.
About Discuss Dropbox Developer & API
Make connections with other developers
