Hello! Question, not an issue... I'm kinda a noob at this, but I've followed the demo example, and I've got it working! :)
I will always have to call /authorize first, is that correct?
Will I always be restricted to the single URL Callback as specified in the Fitbit API Setup screen?
In the example.js demo, /callback is executed just fine... it gets profile info.... But, what if I wanted to add another route, say /GetTXCFile?
I guess I'm trying to think of a way where I could have a couple of different routes:
/heartrate
/steps
/getGPSfiles
My ultimate goal though is bulk-downloading the TCX files. I have all the file names, I just don't want to manually download them 1 by 1. So... I'm sure I can create a loop, and use Node's "path" tool... but would you have any ideas on how to capture the XML response, and save it to a file?
Hello! Question, not an issue... I'm kinda a noob at this, but I've followed the demo example, and I've got it working! :)
I will always have to call
/authorizefirst, is that correct?Will I always be restricted to the single URL Callback as specified in the Fitbit API Setup screen?
In the example.js demo,
/callbackis executed just fine... it gets profile info.... But, what if I wanted to add another route, say/GetTXCFile?I guess I'm trying to think of a way where I could have a couple of different routes:
/heartrate/steps/getGPSfilesMy ultimate goal though is bulk-downloading the TCX files. I have all the file names, I just don't want to manually download them 1 by 1. So... I'm sure I can create a loop, and use Node's "path" tool... but would you have any ideas on how to capture the XML response, and save it to a file?