I have a website that runs events. We have a FitBit applcation with a call back url.
Each of our events has a separate URL under the main website url, and would require a separate call back url in the app.
When doing Oauth I notice that if I don't send the callback registered with my application - (if I try to send one for different events) it fails.
the urls would look like this
www.mySite.com/myevent1/returnpage
www.mySite.com/myevent2/returnpage
etc.
Is it possible to either
1. Register new apps in fitbit as events get created on our site via an api rather than manually
2. Add a placeholder in a url that the Fitbit api understand may contain different values
Thanks
Mark
Answered! Go to the Best Answer.
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.
Hi Mark,
Neither of the two options that you mention are supported.
Here, is what you can do:
- Register your application with multiple callback urls, each url on a new line
e.g.
- Pass the appropriate callback url in the 'redirect_uri' param when making authorization requests
Best Answer
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.
Hi Mark,
Neither of the two options that you mention are supported.
Here, is what you can do:
- Register your application with multiple callback urls, each url on a new line
e.g.
- Pass the appropriate callback url in the 'redirect_uri' param when making authorization requests
Best Answer