02-04-2020 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-04-2020 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
When I make a request to any resource I get a internal error. I believe this is an error of the Fitbit Rest API, not my client error. This is happening when I'm using my clients, or even when I'm using the Fitbit client itself (https://dev.fitbit.com/build/reference/web-api/explore).
https://api.fitbit.com/1/user/-/activities/list.json?beforeDate=today&sort=asc&offset=0&limit=100
The following error is returned:
{
"errors": [
{
"errorType": "request",
"fieldName": "n/a",
"message": "Cannot open connection\nPool state: jdbcUrl=jdbc:mysql://prod-api-master.site-ops.fitbit.com:4417/api?statementInterceptors=com.fitbit.hibernate.mysql.ZipkinMysqlStatementTracingInterceptor, numIdle=0, numBusy=6, numUnclosedOrphaned=0, numInUseByStatementDestroyers=6, numTotal=6, maxSize=6, numWaiting=20, numPendingTasks=0, numActiveTasks=0\nSQL query was ???"
}
],
"success": false
}
Answered! Go to the Best Answer.
Accepted Solutions
02-05-2020 09:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-05-2020 09:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @douglasrafaelcg @LucasRochaDev,
We identified an issued yesterday that resulted in the APIs returning 500s for a short period of time and was quickly mitigated. You can check the notes at our status page https://www.fitbitstatus.com/ and subscribe to alerts if you have not done so already.
If you haven't already, please retry your requests.
Let me know if you have any questions.
02-04-2020 14:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-04-2020 14:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
This happened to me too. I even imagined that it was an error of implementation of my clients in my REST API, however when consuming the routes through Swagger Fitbit, the error persists. It would be interesting if this error was resolved as soon as possible.
02-05-2020 09:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-05-2020 09:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @douglasrafaelcg @LucasRochaDev,
We identified an issued yesterday that resulted in the APIs returning 500s for a short period of time and was quickly mitigated. You can check the notes at our status page https://www.fitbitstatus.com/ and subscribe to alerts if you have not done so already.
If you haven't already, please retry your requests.
Let me know if you have any questions.
