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

Subscriber has not been successfully verified.

ANSWERED

Hello,

 

My Subscription Endpoint is like;

http://myapplication.com/SubscriptionHandler.ashx?provider=Fitbit

 

For verification your servers are hitting endpoint attaching ?verify=123 regardless there is already a querystring parameter exists or not. So it is hitting my server like;

 

http://myapplication.com/SubscriptionHandler.ashx?provider=Fitbit?verify=123

 

Can you please fix the issue there if there is already parameter like ?param=1 hit appending &verify=123 ?

 

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

The issue has been resolved. Thanks for reporting. 

View best answer in original post

Best Answer
5 REPLIES 5

Any Plan to fix this issue or we should handle this our own?

Best Answer
0 Votes

Hi reyou,

 

You're right. We'll look into a fix for this case. In the meantime, you can get around this issue by removing the ?provider query string. 

Best Answer
0 Votes

Thanks for your reply.

I need that query string because I filter out providers other than FitBit such as other Health Related Vendors.

I am using same endpoint for different vendors.

Best Answer
0 Votes

@reyou: Apologies for this bug. We hope to have a fix out by Monday.

Best Answer
0 Votes

The issue has been resolved. Thanks for reporting. 

Best Answer