01-16-2019 15:37
01-16-2019 15:37
I reviewed the subscription API documentation and am stuck on how associations are being made between the app I have registered and the clients who will grant my app permissions using OAuth 2.0. From what I gather from the documentation. First, I create a new app for fitbit. Next, I create my endpoint to receive the notification, which must respond with either a 204 or 404 depending upon if the correct verification code is sent. This is where things begin to get confusing. Where it talks about adding a subscription. Am I making this post call:
POST https://api.fitbit.com/1/user/-/apiSubscriptions/320.json
for every user who's data I need notifications for or is this just where I am letting fitbit know which collection paths I want sent to my endpoint, denoted by the subscription id?
Best Answer01-31-2019 17:23
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-31-2019 17:23
Hi @dever_node1
You posted a similar question on this thread: https://community.fitbit.com/t5/Web-API-Development/Subscription-API-process-flow-and-OAuth-2-0-for-... Do you still have questions here?
Gordon
Best Answer