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

No requests from Fitbit for subscriber endpoint verification

ANSWERED

Hi. I'm trying to verify a new subscriber endpoint. Using curl, I confirmed that the expected HTTP status codes are being returned (204 and 404). However, when clicking 'Verify' and monitoring server logs, I do not see any requests actually being sent. 

 

OAuthClientID: 227LJL

 

Any help would be greatly appreciated!

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Hi @jc1117 

 

I see in our logs that we are initiating the verification, but I don't see a response from your subscriber.   Is your subscriber endpoint open such that it can receive traffic from the outside world?  If it cannot, then we will not be able to send the verification codes to your endpoint.   

 

Gordon

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

View best answer in original post

Best Answer
2 REPLIES 2

Hi @jc1117 

 

I see in our logs that we are initiating the verification, but I don't see a response from your subscriber.   Is your subscriber endpoint open such that it can receive traffic from the outside world?  If it cannot, then we will not be able to send the verification codes to your endpoint.   

 

Gordon

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

Hi @Gordon-C 

 

Ah gosh. I forgot that our staging environment was behind a firewall. I'll reach out to my colleague to address the issue. Thanks so much for checking your logs. 

 

Cheers,

J.C.

Best Answer