Skip to main content
Mirobody includes Garmin, Oura and WHOOP integrations. Each deployment needs its own credentials from the vendor’s developer program. Apple Health uses a separate import and client-push workflow.

​
Prepare the connection

  1. Register your application with the vendor.
  2. Configure a public HTTPS callback on your deployment.
  3. Put credentials in the active configuration overlay, not the shipped defaults.
  4. Apply the configuration and authorize the account in the web client.
The callback format is:
The redirect URL in vendor registration must match the configured URL exactly. Oura and WHOOP use OAuth 2.0; the shipped Garmin connection uses OAuth 1.0a.

​
Example configuration

For Docker, save this in the mounted overlay selected by ENV and MIROBODY_CONFIG_FILE. Editing a checkout’s config.devices.yaml does not change the copy inside an existing image. See Configuration.

​
Check synchronization

Apply changes with docker compose up -d, then inspect the app and worker logs:
A provider with missing credentials is skipped. If authorization fails, check the callback URL and credentials. If connected data does not arrive, check worker status and the database connection. The full setup reference includes developer portals, optional endpoints and vendor-specific details.