08-26-2021 12:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2021 12:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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!
Answered! Go to the Best Answer.

- Labels:
-
Subscriptions API
Accepted Solutions
08-27-2021 11:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



08-27-2021 11:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
08-27-2021 11:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



08-27-2021 11:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
08-27-2021 12:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-27-2021 12:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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.
