Subscriber Verification on AWS API Gateway

[bobmccown]

I am currently at a loss after days of struggling to get my API endpoint to pass subscriber verification. I cannot seem to successfully force AWS API Gateway to return 204 and 404 codes respectfully based on the correct or incorrect ?verify query param. I have a GET method set up on the resource, and it returns a 200 if the request is clean and a 500 if I send a purposefully bad request. The end goal of this API is to feed data to a Kinesis stream.

I've tried Mapping Templates in Integration Response, I've tried the same in a MOCK Integration Request. I've had no success. Can someone from Fitbit please provide a more detailed guide on what the verification GET request is sending and expecting, and how to set this up in AWS API Gateway?

[JohnFitbit]

Hi @bobmccown,

Based on the information you provided, it looks like your application is the one returning the 200 and 500 to Fitbit.

When verifying a subscriber, we send 2 requests to the endpoint your application is listening to as documented here. Then, we expect your application to return a 204 for a correct verification code and a 404 for an incorrect verification code.

Can you ensure that you are registering your callback url in AWS correctly to ensure that we send a GET request to your registered endpoint with query param 'verify'?

Also, can you PM me your Client ID so that we can take a look at our logs for these interactions?

Hope to hear from you soon!