Before we can access user-generated data, we first must ask the individual, who we’ll call the “end user”, for access to their data.
How Authorization Works
If you’re familiar with the application/device API relationship, you can skip this next bit.
To gain access to user-generated data, your customers or “end users” must first grant you permission to access their data. To do this, you need a developer account for every data source we support. Sounds daunting, doesn’t it? Never fear! The Validic Implementation team will complete this task for you. By now, your Account Manager will have forwarded you a form you’ll need to complete to start this process. If you haven’t completed it, please do so now. If you have not received this document, please email them now.
This credentialing process can take several weeks to complete, so to help customers deploy faster, we provide a sandbox organization to every customer. So code away! We’ll provide updated credentials once we’re done setting up all the developer accounts.
Accessing the Marketplace
When you first provisioned a user, you’ll notice a link to the Validic Marketplace and a Marketplace token in the response. By using this marketplace URL, you can rapidly request access to the end users data. Just provide the URL, click the icon associated with the application you’d like synced, and follow the prompts as provided by the data source. Once complete, Validic will begin to retrieve, standardize and store data.
{
"id": "59c539c0164f25000199c47d",
"uid": "se178982",
"marketplace": {
"token": "55c28385e0f449d3de01ff5fd3SAMPLE54d8de5b95d6d98fa4524d5ea54b23",
"url": "https://syncmydevice.com?token=55c28385e0f449d3de01ff5fd3SAMPLE54d8de5b95d6d98fa4524d5ea54b23"
},
"mobile": {
"token": "38152fbb32SAMPLE8ebc36a6be1d3256"
},
"location": {
"timezone": "America/New_York",
"country_code": "US"
},
"sources": [
{
"type": "ihealth",
"connected_at": "2017-09-22T16:33:26Z",
"last_processed_at": "2017-09-22T17:34:25Z"
}
],
"status": "active",
"created_at": "2017-09-22T16:26:40Z",
"updated_at": "2017-09-22T16:26:40Z"
}We also offer a JSON representation of the marketplace for customers who want to provide a custom marketplace to their users. The JSON is the same data we use to build our standard marketplace so there won't be a discrepancy in how the connection process works. The JSON can be requested simply by adding "&format=json" to the end of the user's marketplace URL.
Redirect URI Required
When using the custom marketplace, customers should append a redirect_uri query parameter to the connect_url and disconnect_url to ensure users are properly redirected following the connection process, otherwise, the user will be redirected to the standard marketplace.
(We should include a sample connect link with appended redirect_uri parameter. This probably includes moving this section below the &format=json code samples. I have had at least 2 customers request more direction)
The following example shows the JSON representation of an end users marketplace. You can use this JSON to build your own marketplace by using the connect and disconnect URL's to guide the end user through authentication.
https://syncmydevice.com/?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d&format=json[
{
"type": "omron",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/omron.png",
"connect_url": "https://syncmydevice.com/connect/omron?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "tomtom",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/tomtom.png",
"connect_url": "https://syncmydevice.com/connect/tomtom?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "polar",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/polar.png",
"connect_url": "https://syncmydevice.com/connect/polar?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "fitbit",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/fitbit.png",
"connect_url": "https://syncmydevice.com/connect/fitbit?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "garmin",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/garmin.png",
"connect_url": "https://syncmydevice.com/connect/garmin?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "misfit",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/misfit.png",
"connect_url": "https://syncmydevice.com/connect/misfit?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "strava",
"connected": false,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/strava.png",
"connect_url": "https://syncmydevice.com/connect/strava?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "nokia",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/nokia.png",
"connect_url": "https://syncmydevice.com/connect/nokia?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "jawbone",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/jawbone.png",
"connect_url": "https://syncmydevice.com/connect/jawbone?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "ihealth",
"connected": true,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/ihealth.png",
"connect_url": "https://syncmydevice.com/connect/ihealth?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
{
"type": "suunto",
"connected": false,
"logo_url": "//assets.prod.validic.com/cmapi/images/sources/suunto.png",
"connect_url": "https://syncmydevice.com/connect/suunto?token=ae4fdfd364e42137af14b207eSAMPLEbcdefaae7b99e3e49361SAMPLE1eb0d"
},
]
Updated about a month ago
What's Next
| Accessing Data |