Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Solved
Authorization code flow no longer works?
I am posting all required parameters to https://api.dropboxapi.com/oauth2/token but the servers keeps returning a very vague error: REQUEST: POST https://api.dropbox.com/oauth2/token HTTP/1.1...
Thanks for the report! The request payload for /oauth2/token is expected to be delivered with a content type of "application/x-www-form-urlencoded", per RFC 6749 Section 4.1.3. It's possible we may have also been accepting "application/json" though. We'll look into it, but in the meantime, you can switch to "application/x-www-form-urlencoded", which I've confirmed is working as expected.
Also, for reference, but api.dropbox.com and api.dropboxapi.com are supported for this endpoint.
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorI can't seem to find if/when we accepted JSON on this endpoint. Are you sure this previously worked with that content type?
In any case, x-www-form-urlencoded is the right way to call this. Is that working for you?
In any case, x-www-form-urlencoded is the right way to call this. Is that working for you?
Hi Greg,
I think you are right, I recently updated a large chunk of the code when I migrated my plugin from API v1 to v2. The v2 documentation states that RPC enpoints on the api.dropboxapi.com domain accept arguments as JSON in the request body. For that reason I made all API calls to submit the payload in JSON, and that is where the code flow stopped working (which I didn't notice immediately). Either the documentation needs to be very explicit about the expected content type of that call, or the backend needs to be updated to accept JSON and thus provide claimed consistency. If I had a choice I'd go for option #2 as there is probably no valid reason for that particular endpoint not to recognize JSON.
Anyway, thanks for your prompt attention to this issue, I got the code working by reverting the call to form-urlencoded format.
- Greg-DBThanks for confirming that. I'm glad to hear this is sorted out.
The OAuth endpoints are a little different than the API endpoints, so I'll ask the team to clarify the documentation at least. Hi Vladimir,
Glad to hear about the fix. I'm also working on migration from V1 to V2 API. Can you please provide code block of GetAccessToken() using new end point "https://api.dropboxapi.com/oauth2/token".
That would be really helpful.
Thank you.
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
