08-22-2020 14:46 - edited 08-22-2020 14:47
08-22-2020 14:46 - edited 08-22-2020 14:47
Is it possible to send an Access Token Request using a JSON body instead of x-www-from-urlencoded? I can use x-www-from-urlencoded, but it seems JSON would be more consistent with making REST requests from a back-end process.
I tried but I get a 400 with an error message that I need to use x-www-from-urlencoded.
If not, curious - Is it a requirement of the oAuth 2 spec to use x-www-from-urlencoded?
Thanks,
Jeff Humphry
Answered! Go to the Best Answer.
08-24-2020 13:26
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
08-24-2020 13:26
It is not possible to send the parameters for an access token request using a JSON body. As described in the RFC 6749 specification, "
The client makes a request to the token endpoint by adding the following parameters using the "application/x-www-form-urlencoded" format...
Please see the specification linked above for the complete description.
Best Answer08-24-2020 13:26
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
08-24-2020 13:26
It is not possible to send the parameters for an access token request using a JSON body. As described in the RFC 6749 specification, "
The client makes a request to the token endpoint by adding the following parameters using the "application/x-www-form-urlencoded" format...
Please see the specification linked above for the complete description.
Best Answer