06-12-2025 04:51
06-12-2025 04:51
We are having an issue with the token request failing with a 403. This is only happening in one of our environments with a specific clientID. Tested using Fitbit Web API explorer, and curl. Screenshots attached for reference. Any idea what could be the cause?
07-11-2025 15:44
07-11-2025 15:44
Hi @getrealhealth,
Thanks for reporting this and I'll be happy to take a look. Could you please PM me your basic token that you're using in your authorize request? Also, can you tell me what application type your application is set to (Personal/Server/Client)?