We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Dropbox integration with website / api token
Hi
We have integrated Dropbox with our web app and that is working okay for most customers. I think we have an issue with one of our customers and their api token..
When opening our web app as the client, we can see the dropbox files that are already created, but, when we click on them, nothing happens, no error shown. Our app is designed that it downloads files.
Our client has no knowledge of the email account/password used to create the API so we cannot login and check.
So my question is - do you think there is an API issue? Can we contact Dropbox support with the API key and user name (not email) to see if we can resolve this issue?
Kind regards
Carl.
We're happy to help however we can, but we'd need some more information about exactly what isn't working as expected when your app is calling the API.
It sounds like you're saying that the issue occurs when attempting to download a file, so you're probably referring to calling /2/files/download (either directly or via a method in an SDK or library). Is that where this is breaking down? Whenever an API call like this fails, the API would send an error back in the HTTPS response body itself (and then the library/SDK you're using, if any, would translate that to some sort of error object returned or raised to your code). You should be able to check that in your app's code, but you may need to add some more error handling/logging to surface that if it doesn't already do so.
So, if you can share some more information about whatever error or unexpected behavior you're seeing specifically, we'll take a look. Also, please feel free to open an API ticket with whatever details you can share if you'd prefer to contact us for help privately.
- Greg-DB
Dropbox Staff
We're happy to help however we can, but we'd need some more information about exactly what isn't working as expected when your app is calling the API.
It sounds like you're saying that the issue occurs when attempting to download a file, so you're probably referring to calling /2/files/download (either directly or via a method in an SDK or library). Is that where this is breaking down? Whenever an API call like this fails, the API would send an error back in the HTTPS response body itself (and then the library/SDK you're using, if any, would translate that to some sort of error object returned or raised to your code). You should be able to check that in your app's code, but you may need to add some more error handling/logging to surface that if it doesn't already do so.
So, if you can share some more information about whatever error or unexpected behavior you're seeing specifically, we'll take a look. Also, please feel free to open an API ticket with whatever details you can share if you'd prefer to contact us for help privately.
Hi Greg
Thanks for the reply and apologies for the delay in replying.
I am speaking with someone within Support.
Kind regards
Carl.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
