06-27-2014 11:15
06-27-2014 11:15
When trying to add a subscription we are performing a POST /1/user/-/activities/apiSubscriptions/573-activities.xml HTTP/1.1
The response we get back is a HTTP 409-conflict. The error message indicates that we can’t add a listener for user 573 because we already have one for user 532. The contents of the response look like this: <?xml version="1.0" encoding="UTF-8"?><result><collectionType>activities</collectionType><ownerId>2GQL33</ownerId><ownerType>user</ownerType><subscriberId>1</subscriberId><subscriptionId>532-activities</subscriptionId></result>
Why does it matter that we have an activity subscription for 532 (called 532-activities) when we are now trying to add 573-activities? We want to use 1 subscriber URL for all of our user subscriptions and that URL is already registered with our "fitbit application". What are we missing or doing wrong here?
Thanks in advance!
Answered! Go to the Best Answer.
06-27-2014 12:16
06-27-2014 12:16
Hello.
Are you sure you using access token for user 573?
Try execute http://api.fitbit.com/1/user/-/profile.json request and check if it returns to you the user that correspond to 573. The encoded id should NOT be equal to 2GQL33, since 2GQL33 correcponds to 532 according to your message.
06-27-2014 12:16
06-27-2014 12:16
Hello.
Are you sure you using access token for user 573?
Try execute http://api.fitbit.com/1/user/-/profile.json request and check if it returns to you the user that correspond to 573. The encoded id should NOT be equal to 2GQL33, since 2GQL33 correcponds to 532 according to your message.
07-08-2014 05:55
07-08-2014 05:55
Thank you for your help! This pointed us in the right direction and we were able to resolve our issue.