Cannot verify subscriber endpoint

[irh_dev]

Hello,

Having an issue over here ... can't verify our subscriber endpoint. I've moved the implementation away from where it was implemented before, so I made some changes to the URL. Postman is reporting that my implementation is returning the appropriate 204's & 404's ... 

The base of our subscriber is:

https://api.our-company.com/resources

Assuming that you're adding '/fitbit/' that I see in the documentation. I've switched now to using the subscriber URL:

https://api.our-company.com/resources/fitbit

I'm listening to these two:

GET https://api.our-company.com/resources/fitbit/webhook?verify=correctVerificationCode

GET https://api.our-company.com/resources/fitbit/webhook?verify=incorrectVerificationCode

And returning 204's & 404's. This is an AWS Lambda/API Gateway implementation, and AWS Route 53 has given me the certificate for our site. 

No stats are being provided on the dev website every time I try "Verify", so I was hoping you could get more information out of your system.

Thanks,

Carmine

[irh_dev]

I can provide our actual company name so that you could test it on your side ... I just didn't want to leave it in the post.

[irh_dev · Accepted solution]

Ah ... I find your documentation confusing.

GET https://yourapp.com/fitbit/webhook?verify=correctVerificationCode

https://dev.fitbit.com/docs/subscriptions/#verify-a-subscriber

At no other time in your documentation do you refer to this URL as an example. I assumed that you needed "webhook" appended to the subscriber URL. I'd recommend sticking with one example URL, and clearly indicating it as such.

I got it to work, thanks.