Endpoint not successfully verified

[Get2Requests]

Setting up FitBit auto-syncing.

We do see the 2 requests in the IIS logs, but the endpoint is still not being verified. We use a proxy server and redirect to the server we want, which is not externally accessible.

Both are GET request and one is a 204 and the other is a 404. The verification code for the 204 matches up with what is on the FitBit site.

[AndrewFitbit]

@Get2Requests Are you replying back to the GET requests with the appropriate 204 and 404 responses?

[Get2Requests]

Yes, it is responding with a 204 and 404

[jlin]

Andrew, We are seeing the same issue as well, how can we proceed to find the issue? I can provider more information if it is needed.

[Get2Requests]

@JeremiahFitbit

Could we get a response to this issue?

[AndrewFitbit]

@Get2Requests @jlin Send me your subscriber endpoint url via PM.

[HM_Ambulatory]

Greetings - we are experiencing this issue at Houston Methodist. I would appreciate learning about any new findings. Thanks!

[jlin]

We still can't fix the issue (Get2Requests has sent you the endpoint, we are together). May I ask if we can get the same kind of feedback as we have for notifications so that we know where is the problem?