Device Connections
Deregister Connection
DELETE
/
v2
/
user
/
{user_id}
/
{provider}
Deregistration has well-defined behaviour only on cloud-based providers.
While you can call this endpoint against these SDK-based providers, Vital Mobile SDK would automatically “reconnect” on the next data sync attempt.
We do not have a “disconnect” mechanism for SDK-based providers at this time.
You can pause Health SDK data sync client-side, or sign-out the user from the SDK.
Authorizations
x-vital-api-key
string
headerrequiredVital Team API Key
Path Parameters
user_id
string
requiredprovider
enum<string>
requiredProvider slug. e.g., oura
, fitbit
, garmin
.
Available options:
oura
, fitbit
, garmin
, whoop
, strava
, renpho
, peloton
, wahoo
, zwift
, freestyle_libre
, abbott_libreview
, freestyle_libre_ble
, eight_sleep
, withings
, apple_health_kit
, manual
, ihealth
, google_fit
, beurer_api
, beurer_ble
, omron
, omron_ble
, onetouch_ble
, accuchek_ble
, contour_ble
, dexcom
, dexcom_v3
, hammerhead
, my_fitness_pal
, health_connect
, polar
, cronometer
, kardia
, whoop_v2
, ultrahuman
, my_fitness_pal_v2
, map_my_fitness
Response
200 - application/json
success
boolean
requiredWhether operation was successful or not