Connecting Users to Inform Connect

📘

To complete the steps on this page you must be issued Inform Connect API credentials by Validic.

Please complete our Inform Connect interest form if you'd like to learn more about the Connect APIs.

To submit data to Inform as a Data Source Partner, five basic steps must be completed:

Step 1: End User clicks “Connect” in Inform Marketplace. This occurs in the Client organization’s application.
Step 2: End User is redirected to the Data Source’s site for authentication. End User logs in to the Data Source’s site and confirms their request to connect to the Validic Organization. Step 3: Data Source requests an Inform Connect user access token. Inform Connect responds to Data Source with an access token. Step 4: Data Source returns the End User to their Inform Marketplace using the redirect url.
Step 5: Data Source posts data to the Inform Connect API for the End User.

These steps allow the End User, your user, to grant our Clients access to their data, and opens the way for your integration to submit data to Inform on their behalf. The rest of the sections on this page detail the first four steps of this process, which is the process for managing Inform user connections.

Step 1: End User clicks Connect in Inform Marketplace

Each Validic User is presented with a “marketplace” of apps and devices that they can share data from. The Inform Standard Marketplace is a simple, responsive webpage that contains each Data Source's branding and an option to connect to your app or device. Validic also offers an Inform Unified Marketplace, which is a JSON representation of the standard marketplace that can be used by Validic Client organizations to render the Marketplace in their own web or mobile application, creating a more seamless workflow for Users to connect devices.

📘

This Marketplace is made available to the End User from the Client Organization's user experience, like a Client's mobile app or web app.

There's nothing the Data Source Partner needs to do in this step; just be aware that this is how the End User starts the connection workflow.

Step 2: End User is redirected to Data Source for authentication

Once the End User selects “Connect” from the Marketplace, they’ll be directed to an OAuth URL hosted by you as the Data Source Partner.

When the End User is redirected to your OAuth URL, you will find the url contains the following parameters:

• session_token: the universally unique identifier, (UUID) for the user’s connection session. This user’s connection session will be validated by Marketplace when the Inform Connect Data Source attempts to request a user access token. The session token is valid until the connection process is completed or will expire after 10 minutes.
• organization: Base64-encoded Client organization name. This identifies the Validic Client Organization which the End User belongs to. This the Client that the End User wants to share data with.
• redirect_url: Base64-encoded URL used by the Inform Connect Data Source to redirect the End User back to the correct Marketplace after the OAuth process is completed.
  • The base URL format is: https://syncmydevice.com/auth/**DataSourceName**/**callback**
  • The Inform Connect Data Source must decode this value and append a status parameter (status=success or status=failure) to indicate the result of the connection attempt.
  • An error parameter may also be included to return an error message string.

Example OAuth URL:

http://connect.yourcompany/auth?session_token=aed5cfb3-eba5-439b-af24-5f45076b2853&organization=VmFsaWRpYyBEZXZz&redirect_url=aHR0cHM6Ly9tYXJrZXRwbGFjZS5zdGFnZS52YWxpZGljLmNvbS9hdXRoL3ZhbGlkaWNfY29ubmVjdF90ZXN0L2NhbGxiYWNr

Step 3: Data Source requests User Access Token

Once the End User has granted the Client Organization access to their data, you as the Data Source must complete the authorization process with Inform Connect and store the user's access_token and validic_user_id. This process involves manually executing a POST request for the user access token to Inform Connect.

Request User Access Token

You’ll need to POST to https://syncmydevice.com/connect/token

Required Headers

Content-Type: application/json  
Authorization: Basic dmFsaWRpY19jb25uZWN0X3Rlc3Q6YWJjMTIzNjk5YmVlMTQ5NTNhNjFkYzE2YTFkMDNlWg==

NOTE: The authorization token is Base64-encoded from the Connect Partner Name and Client Secret provided to you by the Validic team.

For example, if:

Connect Partner Name = validic_connect_test
Client Secret = abc123xyz

To generate the authorization token,

Base64-encode <Connect Partner Name>:<Client Secret> 

The resulting authorization token for this example would be: dmFsaWRpY19jb25uZWN0X3Rlc3Q6YWJjMTIzeHl6

Request Body

{
  "uid": "uid_for_user",
  "session_token": "value_copied_from_step1"
}

Request Response

This request should return 201 Created and the following body.

{
    "access_token": "access_token_value",
    "validic_user_id": "validic_user_id",
    "expires": false,
    "created_at": "2025-12-30T17:53:32Z"
}

The access_token returned here is scoped to the End User’s connection to your Data Source and this access_token is required to POST health data to the Inform Connect API.

Step 4: Return End User to Marketplace Using Redirect URL

Now that you’ve received and stored the user’s Inform Connect access_token, use the redirect_url OAuth URL parameter to direct the End User back to the Marketplace.

🚧

Don’t forget to append a status parameter (status=success or status=failure) to indicate the result of the connection attempt.

Example Redirect URL for a successful connection: https://syncmydevice.com/auth/validic_connect_test/callback?status=success

Example Redirect URL for an unsuccessful connection: https://syncmydevice.com/auth/validic_connect_test/callback?status=failure&error=user%20authorization%20cancelled

When you pass back a status=success the End User is now connected in Validic Inform to the Client Organization and you may proceed to POST the End User’s data to the Validic Inform Connect API. See Submitting Health Data to Inform Connect for details.