09-14-2016 07:39
09-14-2016 07:39
Any help?
It was working normally.
REQUEST
POST /oauth2/token
RESPONSE
{HTTP/1.1 404 Not Found
[Date: Wed, 14 Sep 2016 14:20:01 GMT,
Content-Type: text/plain,
Content-Length: 9,
Connection: keep-alive,
X-Gateway-Error: BACKEND_ROUTE_UNAVAILABLE,
X-Frame-Options: SAMEORIGIN,
Server: cloudflare-nginx,
CF-RAY: 2e247a2a3f000893-FRA]}
09-14-2016 08:12
09-14-2016 14:33
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.
09-14-2016 14:33
@fitfittt: We're investigating reports of this. Does retrying the request result in a successful response?
Best Answer09-14-2016 15:48
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.
09-14-2016 15:48
@fitfittt: Can you capture the full HTTP request? You could use a tool like Runscope Traffic Inspector.
I'm curious to know if you're using HTTP/1.1 and sending a Host header. The first two lines should look like:
POST /oauth2/token HTTP/1.1 Host: api.fitbit.com
Best Answer