Device Providers

Provider slugs, hosted authorization, and the cloud connection lifecycle.

The current API connects cloud accounts exposed by supported wearable, fitness, nutrition, and health-device providers. Query the provider catalog at runtime rather than maintaining a static list in your integration.

Provider Catalog

{
  "providers": [
    {
      "slug": "garmin",
      "name": "Garmin",
      "thumbnail_url": "https://media.sonarhealth.co/devices/Garmin.jpg"
    }
  ]
}

Use slug as the provider in connection and disconnection requests. thumbnail_url is nullable. The provider picker in Developers → Users → Connect device reads the same catalog, so API clients and Atlas stay aligned as availability changes.

Providers Available Today

Sonar’s cloud provider catalog includes the direct integrations listed below.

Sonar’s mobile SDKs extend this coverage through Apple Health, Google Health Connect, and Samsung Health, connecting your application to a broader ecosystem of thousands of health and fitness apps and connected devices. Data availability depends on the supported data each source shares with these platforms and the permissions granted by the user.

This table is a documentation snapshot. Use GET /v1/providers when your application needs the current catalog.

Connection Lifecycle

Retrieve the user with GET /v1/users/{id} to inspect its connections, including each provider’s status, connection timestamp, and latest synchronization timestamp. Webhook events remain the push interface for connection and synchronization changes.

Historical data can arrive across multiple subject.synced events. Providers do not supply a reliable terminal signal, so Sonar does not emit a separate event claiming that historical ingestion is complete.

Multiple Providers

A user may connect more than one provider. Sonar consolidates their source data before serving daily values. The public response is the normalized result and does not expose raw provider payloads or per-value source attribution.

Go Deeper