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

Creating a new subscriber isn't getting a unique ID

We're implementing subscriber notifications but can't seem to get it working consistently. It works with a single test user, we can get notifications properly, but the moment we add a second test user, that user get's the exact same subscriber ID as the first one (which is a 1), and then we stop getting notifications altogether.

 

Our subscription endpoint ID is "1", wasn't sure what else to name this for now, but for details-sake:

 

Test account1 user ID: 4TK4ZQ

Test account1 subscriberID: 1

Test account1 subscriptionID: 1

 

Test account2 user ID: 22KSTD

Test account2 subscriberID: 1

Test account2 subscriptionID: 1

 

Tried deleting and re-adding, continues to get the same sub ID and notifications stop arriving. 

Best Answer
0 Votes
1 REPLY 1

Hi @Jer_TX,

 

When adding the subscription for the second user, your application should have received a "409 Conflict" error.  In the documentation, we state "Each [subscription] ID must be unique across the entire set of subscribers and collections."  Therefore, you can't have both users assigned to the same subscription ID.  Your configuration needs to be something like

 

Test account1 user ID: 4TK4ZQ

Test account1 subscriberID: 1

Test account1 subscriptionID: 1

 

Test account2 user ID: 22KSTD

Test account2 subscriberID: 1

Test account2 subscriptionID: 2

 

 

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes