05-11-2021 18:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-11-2021 18:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
The subscription verification for our application is failing and showing this message "Subscriber has not been successfully verified."
The endpoint is working fine and it is returning the correct 204/404 replies when the code is either correct or invalid.
I tried hitting the verify button several times but the subscription is not getting verified.
Oauth client id: 22C4VD
What i'm doing wrong ?
This is critical for us. Please look into it asap.
Thanks in advance.
Answered! Go to the Best Answer.

- Labels:
-
Subscriptions API
Accepted Solutions
05-13-2021 09:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-13-2021 09:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @changhc
Once your subscriber is verified, you'll reference the subscriber ID when adding a subscription. See https://dev.fitbit.com/build/reference/web-api/subscriptions/#adding-a-subscription. If your application has multiple subscribers, referencing the subscriber ID when adding the subscription let's Fitbit know which subscriber to send the notification.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
05-12-2021 10:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-12-2021 10:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @changhc
In our logs I see your subscriber is sending a 404 when we send you the correct verification code. You should be replying with a 204. Would you please verify this in your code?
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
05-12-2021 18:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-12-2021 18:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @Gordon
I checked 204 when sending the value set by Subscriber ID and 404 when not.
Isn't the verification code Subscriber ID?
05-12-2021 19:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-12-2021 19:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @Gordon
I checked the log and found a value other than the Subscriber ID set by the verification code, so I modified it and processed it.
Where do I use the Subscriber ID I set ?

05-13-2021 09:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-13-2021 09:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @changhc
Once your subscriber is verified, you'll reference the subscriber ID when adding a subscription. See https://dev.fitbit.com/build/reference/web-api/subscriptions/#adding-a-subscription. If your application has multiple subscribers, referencing the subscriber ID when adding the subscription let's Fitbit know which subscriber to send the notification.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
