Stel Life Direct Connection - Eliminate User Setup
Connecting The Stel Vitals Hub via the Validic Marketplace is easy. Instead of the typical cloud account linking workflow, users simply enter their Stel hub’s unique Hub Identifier and they’re done.
However, an even easier user setup workflow is available for cellular sources like Stel. Validic Inform clients can build a workflow using Direct Connection API calls to automatically connect their users to Stel - without requiring the user to enter anything into the Validic Marketplace.
Direct Connection offers benefits such as:
Setup-free workflow: User interaction is not required to connect the cellular device. Virtually no setup is needed by the user.
App-optional experience: User is not required to use a smartphone to connect or sync readings.
API-based implementation: Clients can implement Direct Connection using simple JSON APIs.
This page details how the Direct Connection APIs work for Stel. To learn more about the Inform integration to Stel, please see Stel Life Cellular API Integration.
User Authorization for Stel Cellular Hubs
Overview
End users cannot purchase Stel Vitals Hub directly from Stel Life. These hubs must be acquired through a client who has signed a contract with Stel or Validic Logistics. Validic Inform does not have access to the PHI necessary to ship devices, therefore Inform clients using Stel Life hubs are responsible for acquiring the devices and distributing them to patients/users through their own workflow or Validic Logistics.
This guide details the Inform APIs that clients will need to implement in order to create and manage the data connection between Stel and Validic Inform on behalf of the end user. The required steps are:
Provision a user in Validic Inform
Establish the user device connection between Stel and Validic Inform
Receive Stel hub data in Validic Inform
We also cover disconnecting the user’s Stel hub connection, in case the user leaves your program.
Let’s get into the individual steps.
Provision User in Validic Inform
Sample Request
Content-Type: application/x-www-form-urlencoded
POST https://api.v2.validic.com/organizations/:orgid/users?token=:token
{
"uid":"277040620sol3"
}
Where:
:orgid is the Validic Organization ID to associate the user with
:token is the Organization access token
uid is the client’s user identifier
Sample Response
{
"id": "59b0664cf758800001e13ea9",
"uid": "277040620sol3",
"marketplace": {
"token": "ee889ef9d7fb7a9644c97ef9d69ZSAMPLEa0be23352bdee46a775c066ef0f890",
"url": "https://syncmydevice.com?token=ee889ef9d7fb7a9644c97ef9d69ZSAMPLEa0be23352bdee46a775c066ef0f890"
},
"mobile": {
"token": "7c001f84255SAMPLE8c168ba563035"
},
"sources": [],
"created_at": "2023-07-06T21:19:08Z",
"updated_at": "2023-07-06T21:19:08Z"
}
Establish User Device Connection via Direct Connection API
Sample Request
Content-Type: application/json
POST https://syncmydevice.com/direct/auth/stel/connect?token=:token
{
"device_id": :deviceID
}
Where:
:token is the user’s marketplace token
:deviceID is the Stel hub identifier (see Note 2 below)
Note:
All values are strings
device_id is the 10-digit alphanumeric identifier found on the back of the Stel hub or its packaging
Example Request Body
{
"device_id": "8ZFGDTESTC"
}
Sample Response
{
"credentials": {
"device_id": "8ZFGDTESTC",
"device_type": "hub",
"device_name": null
},
"type": "stel",
"created_at": "2025-02-06T17:57:43Z"
}
When enabled, Stel also appears in your Validic Inform Marketplace. If users connect via the marketplace, they will be routed to a screen to enter their 10-digit alphanumeric hub identifier manually, which will also connect them to Stel.
If you want to prevent users from seeing Stel as an option in the marketplace you’ll want to either avoid routing the user to the marketplace or hide the Stel (stel) source from your user’s view using the Custom Marketplace.
Disconnect User via Direct Connection API
Disconnecting the user from Stel can be done in two ways:
Disconnect a single hub from the user - this leaves any other Stel hubs connected to the user and only removes the hub indicated.
Disconnect all hubs from the user - this disconnects all Stel hubs from the user at once.
Note: It’s not common that a user would have more than one Stel hub, but Inform does let you connect more than one to a single user if you need to.
Disconnect a single hub
Sample Request
POST https://syncmydevice.com/direct/auth/stel/disconnect/:device_id?token=:token
Where:
:device_id is the Stel hub identifier (see Note 1 below)
:token is the user’s marketplace token
Note:
The device_id is a 10-digit alphanumeric identifier found on the back of the Stel hub or its packaging
If the user has multiple Stel hubs to disconnect then multiple requests must be made, one for each hub. Or you can disconnect all Stel hubs at once using the Disconnect All Devices API in the section below.
Example Request
POST 'https://syncmydevice.com/direct/auth/stel/disconnect/8ZFGDTESTC?token=02f0c59b63310f7cec951aSAMPLEdd15481ec1dfd5f7e1f6927'
Sample Response
{
"credentials": {
"device_id": "8ZFGDTESTC",
"device_type": "hub",
"device_name": null
},
"type": "stel",
"created_at": "2025-02-06T19:11:59Z",
"deleted_at": "2025-02-06T19:15:05Z",
"deleted_reason": "User disconnected from Direct Endpoint"
}
Disconnect all hubs
Sample Request
POST https://syncmydevice.com/direct/auth/stel/disconnect_all?token=:token
Where:
:token is the user’s marketplace token
Note:
This endpoint will disconnect all Stel hubs for the given user. If you only want to disconnect a specific hub then the Disconnect A Single Hub API in the section above should be used.
Example Request
POST 'https://syncmydevice.com/direct/auth/stel/disconnect_all?token=02f0c59b63310f7cec951aSAMPLEdd15481ec1dfd5f7e1f6927'
Sample Response
{
"meta": {
"total": 2
},
"connections": [
{
"credentials": {
"device_id": "8ZTEST7H1C",
"device_type": "hub",
"device_name": null
},
"type": "stel",
"created_at": "2025-02-06T17:57:43Z",
"deleted_at": "2025-02-06T19:18:48Z",
"deleted_reason": "User disconnected from Direct Endpoint"
},
{
"credentials": {
"device_id": "ABCD1234TC",
"device_type": "hub",
"device_name": null
},
"type": "stel",
"created_at": "2025-02-06T19:16:57Z",
"deleted_at": "2025-02-06T19:18:48Z",
"deleted_reason": "User disconnected from Direct Endpoint"
}
]
}
Stel Data
The Stel Life Inform integration has the source ‘type’: stel
The Stel Life Inform integration supports the devices listed on the Stel Life API integration page.
The Stel Inform integration supports the data metrics defined on the Standard Metrics Used Per App page (see “Stel Life” app).
Sample Data
The below example illustrates a single weight measurement using the Stel hub with an A&D UA-651BLE blood pressure monitor. This sample shows how these readings appear in the Validic Inform Streaming API and REST API.
{
"checksum": "b0a2547d56SAMPLE5d57437a90b",
"created_at": "2025-01-10T17:20:04.858Z",
"deleted_at": null,
"end_time": "2025-01-10T15:58:56Z",
"id": "3de314260ccSAMPLE69c5bae6547f1",
"log_id": "5b32e76b-d33b-431f-9522-4dd1a4183e2b",
"metrics": [
{
"origin": "device",
"type": "diastolic",
"unit": "mmHg",
"value": 73.0
},
{
"origin": "device",
"type": "systolic",
"unit": "mmHg",
"value": 112.0
},
{
"origin": "device",
"type": "pulse",
"unit": "bpm",
"value": 91
}
],
"offset_origin": "source",
"source": {
"device": {
"diagnostics": [],
"id": null,
"manufacturer": "a&d",
"model": "ua-651ble (blue)"
},
"type": "stel"
},
"start_time": "2025-01-10T15:58:56Z",
"tags": [],
"type": "measurement",
"user": {
"organization_id": "5ef0ef69SAMPLEba562",
"user_id": "652572SAMPLEe18b8b8",
"uid": "123456"
},
"user_notes": [],
"utc_offset": -14400,
"version": "1.0"
}
Details on using the Inform Streaming API and REST APIs can be found in our online technical documentation.