使用python-fitbit调用Fitbit API获取心率数据时遇HTTPBadRequest错误

Looks like you’re hitting a common pitfall with the time_series method in the python-fitbit library. Let’s break down what’s going wrong and how to fix it quickly.

The Issue with Your Current Call #

Your code has two key problems that are triggering the Fitbit API’s bad request response:

• You’re passing a full API URL to the time_series method, but the library already handles the base https://api.fitbit.com/1/user/-/ path automatically. Adding the full URL creates a malformed request.
• You’re combining a date range (today/1d) in the path with a period="1d" parameter. Fitbit’s API doesn’t allow mixing these two ways of defining a time window — it’s redundant and causes a parameter conflict.

Correct Ways to Fetch Heart Rate Data #

Replace your current call with either of these valid, simplified options:

Option 1: Use Date Range (No Period Parameter) #

client.time_series("activities/heart", base_date="today", end_date="1d")

Option 2: Use Period Parameter (No End Date) #

client.time_series("activities/heart", base_date="today", period="1d")

Both of these will correctly request 1 day of heart rate data ending today, without conflicting parameters or redundant URL parts.

Additional Troubleshooting Tips #

If you still run into issues after fixing the call, double-check these:

• OAuth Scopes: Ensure your app requested the heartrate scope when generating the access token. If this scope isn’t included in your token’s permissions, the API will reject heart rate requests even if other data (like sleep) works.
• Rate Limits: Fitbit’s API enforces rate limits. If you’ve made too many requests in a short window, you might get a bad request response. Wait a few minutes and try again if this is the case.

内容的提问来源于stack exchange，提问作者shachar10