Get Temperature (Core) Summary by Date
This endpoint returns the Temperature (Core) data for a single date. Temperature (Core) data applies specifically to data logged manually by the user throughout the day.
It uses units that correspond to the Accept-Language header provided.
Scope: temperature
Request
| GET | /1/user/[user-id]/temp/core/date/[date].json |
URI Arguments
| user-id | required | The encoded ID of the user. Use "-" (dash) for current logged-in user. |
| date | required | The date in the format yyyy-MM-dd or today. |
Request Headers
| authorization | required | Specify the token type and Fitbit user’s access token. Token type: Bearer |
| accept | optional | The media type of the response content the client is expecting. Supported: application/json |
| accept-language | optional | The measurement unit system to use for response values. See Localization. |
| accept-locale | optional | The locale to use for response values. See Localization. |
Examples
GET https
-H "accept: application/json" \
-H "authorization: Bearer <access_token>"
Response
| Element Name | Description |
| tempCore : dateTime | The log timestamp specified in the format YYYY-MM-DDThh:mm:ss. |
| tempCore : value | The temperature value in degrees Celsius or Fahrenheit depending on the country specified in the Accept-Language header. |
{
"tempCore": [
{
"dateTime": "2020-06-18T10:00:00",
"value": 37.5,
},
{
"dateTime": "2020-06-18T12:10:00",
"value": 38.1,
},
]
}
Response Headers
| content-type | The media type of the response content being sent to the client. Supported: application/json |
| fitbit-rate-limit-limit | The quota number of calls. |
| fitbit-rate-limit-remaining | The number of calls remaining before hitting the rate limit. |
| fitbit-rate-limit-reset | The number of seconds until the rate limit resets. |
Note: The rate limit headers are approximate and asynchronously updated. This means that there may be a minor delay in the decrementing of remaining requests. This could result in your application receiving an unexpected 429 response if you don't track the total number of requests you make yourself.
Response Type
| HTTP Status Code | HTTP response code. List of codes are found in the Troubleshooting Guide. |
| Status Message | Description of the status code. |
| Response Body | Contains the JSON response to the API call. When errors are returned by the API call, the errorType, fieldName and message text will provide more information to the cause of the failure. |
Response Codes
| 200 | A successful request. |
| 400 | The request had bad syntax or was inherently impossible to be satisfied. |
| 401 | The request requires user authentication. |
Note: For a complete list of response codes, please refer to the Troubleshooting Guide.
Additional Information
Subscription Support for Temperature (Core)
Temperature (Core) does not support subscription notifications (webhooks). This data is manually entered by the user, so we don’t believe it will change frequently. We recommend querying Temperature (Core) data once or twice a day to determine if new data is available (e.g. 12 noon and midnight). However, the frequency or rate at which you query Temperature (Core) data should be based on your specific use cases and with this in mind.
Rate limit
The Temperature (core) endpoints are bound by our standard rate limit. See Rate Limits.
Device compatibility
Temperature (Core) data is retrieved from the user’s Fitbit account. This gives the user secure and transparent control over their data. The data is then processed and made available through the API after the user syncs their device with the Fitbit data service.
Most of the current devices sold support SpO2 data collection. See the Fitbit Product page to determine if your specific device supports SpO2.
