Legacy Fitbit Web API rejects valid 7-character user IDs returned by profile endpoint
We are seeing an inconsistency in the legacy Fitbit Web API for newly created users.Calling:GET /1/user/-/profile.jsonreturns an encodedId such as:98AV5X7But calling:GET /1/user/98AV5X7/body/log/weight/date/YYYY-MM-DD.json (date was anonymized as it...