Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HTTPS required for callback URL?

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?

Best Answer
0 Votes
3 REPLIES 3

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.

 

 

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes

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

Best Answer
0 Votes

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

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes