12-15-2018 09:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-15-2018 09:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I've been using http://localhost:PORT/callback as my callback url for testing, but when I try to edit it to http://somehost:PORT/callback for deployment, I'm seeing an error message saying HTTPS is required.
However when I hover beside the field for callback url, the tooltip text says HTTPS is recommended but not required. Am I missing something?
12-17-2018 15:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



12-17-2018 15:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @someuser101. We have restricted the callback URL to support HTTPS only. The information in the tooltip is outdated. Thank you for pointing that out.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

01-20-2019 22:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

01-20-2019 22:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @Gordon-C. Has callback URL been restricted to support HTTPS only across all platforms? I have some users on iOS that are experiencing 404 errors on authorization, and the callback URL is currently just a standard iOS callback URL (myappscheme://). However, it still works for a number of users - I'm not sure why it would work for some and not all. Thanks in advance for the help

01-22-2019 10:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



01-22-2019 10:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @jonbee75,
The callback URL for web apps should be HTTPS. However, I believe your problem is related to something else. Your callback URL needs to be an absolute URL, meaning it needs to look like myappscheme://callback.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

