Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
Currently during authentication retyrned URL contains token_type=bearer parameter while respective header must be Bearer (else 400 is returned).
Is that possible to return correct case in token_type so one could just use it in header? Or it is by-design and developer must always implement own mapping for auth types like bearer->Bearer ?
According to the documentation, we only support the "bearer" token type, so any of these should be fine.
Thanks for the post! I can't speak to the intent here, but I'll send this along to the team to see if we can get that changed. I can't make any promises as to if they will do so though.
Thank you, Greg, for response.
Even it this is intensionally and won't be changed in future, I would appreciate advices of the parameter usage:
According to the documentation, we only support the "bearer" token type, so any of these should be fine.
Hi Greg,
the api does not accept "bearer", it only accepts "Bearer".
the returned value in token_type is "bearer" and most oauth clients will use that value to compose the Authorization Header.
the result is that the Authorization being sent to subsequent requests has the Authorization header "Authorization: bearer xxxxx" instead of "Authorization: Bearer xxxxx".
it seems to me that, the token_type value returned should be "Bearer" instead of "bearer" if api only accepts that, or change the api to accept "bearer".
thoughts ?
@lazedo Thanks for the post. I'm not aware of any current plans to change this, but I'll add your vote to the request.
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!