05-23-2025 03:47 - edited 05-25-2025 23:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-23-2025 03:47 - edited 05-25-2025 23:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
- Error Code: 403
- Error Message: "The caller does not have permission"
- API Endpoint: POST /1/user/-/body/log/weight.json
- Authorization Scopes: I've requested and received all necessary permissions, including the weight scope.
- Token Validity: My access token is valid and has not expired.
Answered! Go to the Best Answer.
Accepted Solutions
05-29-2025 01:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-29-2025 01:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @haoziy
Apologize for any inconvenience you're experiencing with this issue. I've reported this to our engineering team and will be sure to provide an update as soon as I receive one.
Workaround Solution: You'll need to append your user_Id directly to the URL. For example, please change the URL from: https://api.fitbit.com/1/user/-/body/log/weight.json to: https://api.fitbit.com/1/user/user_Id/body/log/weight.json
Regards,
Inca
05-23-2025 13:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


05-23-2025 13:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
(Post moved to Web API forum section.)
Gondwana Software
05-25-2025 11:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-25-2025 11:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Also hitting this issue. Any updates from Fitbit?
05-25-2025 23:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-25-2025 23:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
what’s your issue detail

05-29-2025 01:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-29-2025 01:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @haoziy
Apologize for any inconvenience you're experiencing with this issue. I've reported this to our engineering team and will be sure to provide an update as soon as I receive one.
Workaround Solution: You'll need to append your user_Id directly to the URL. For example, please change the URL from: https://api.fitbit.com/1/user/-/body/log/weight.json to: https://api.fitbit.com/1/user/user_Id/body/log/weight.json
Regards,
Inca
