Alternative Ways to Integrate
Notebook Editor Links
The FitnessSyncer API is great for creating complex applications, but the foundation can also be done to create simple tasks. For example, let’s say that you want to create a reminder to do a certain activity and upon completion, you want to save the context behind this activity; you can do this by creating a link to the FitnessSyncer Notebook.
To do this, you will need to determine which type of data you wish to save; for example, if you wish to save a new Activity, you would refer to the Activity type and the SyncItem type.
Using this definition, all fields which are of type String, Integer, or Double can be passed into the FitnessSyncer Notebook Editor’s query string.
Here is an example to log 10 push-ups, taking 1 minute, and burning 5 calories to the FitnessSyncer Notebook:
https://www.fitnesssyncer.com/notebook-editor?new&taskType=Activity&repetitions=10&duration=60&calories=5&activity=Push%20UpsThese links honor API Versions the same way the rest of the API does, and you may append apiVersion to the query string. As with the API, every field name we have ever accepted keeps working.
If you have any questions on how to use this feature, please contact us.
Cloud Storage
An alternative integration to using our full API is to use Cloud Storage. Configuring a Cloud Storage Provider as a destination with the FitnessSyncer API format lets you export health and fitness data to a folder and consume it using our data model, without a direct integration with FitnessSyncer.
For example, you could configure a Sync Destination task to export data to Amazon S3 using {id} as the filename and FitnessSyncer API as the output. This creates files named {id}.fsapi, which you can then read using our schema — an Activity record, for instance, would match the Activity type and the SyncItem type.
If you have any questions on how to use this feature, please contact us.
MCP
FitnessSyncer exposes an MCP server so that you can use FitnessSyncer from popular AI Assistants. To learn more, see our documentation.
Quick Setup Links
If all you want is for your users to arrive at FitnessSyncer with the right connections already set up, you do not need to call the API at all. A Quick Setup link does the whole thing: it signs the user in or creates their account, adds the sources and destinations in your link, walks them through authenticating each one, and returns them to you.
Put a link like this on your own site:
https://www.fitnesssyncer.com/quick-setup?sources=Withings:Weight,Fitbit:Activity&destinations=TrainingPeaks:ActivityThe parameters are:
| Parameter | Required | Description |
|---|---|---|
| sources | One of these | A comma separated list of the services to read from, each written as Provider:TaskType. You can see the available values by listing providers and reading the data types. |
| destinations | One of these | The same, for the services to write to. A link may name sources, destinations, or both, so long as it names at least one. |
| partner | No | Your partner identifier, which adds your name and logo to the page, applies the connection defaults we have configured for you, and puts a button at the end that returns the user to you. |
| template | No | Which of your configurations to apply, when you have more than one. Defaults to the one named default. |
The task type is required on every entry. Most services carry several kinds of data.
Anything the user already has is left alone. If they have connected a service before, we re-use that connection rather than asking them to authorize it again, and a connection they had turned off is offered back to them. Every step can be skipped, and nothing is ever removed.
The address we return the user to is part of your partner configuration rather than the link, so that it cannot be used to send your users somewhere you did not intend. Please contact us to set up a partner identifier, your logo, your return address, and the defaults you want applied.
