Provider onboarding

Every health platform Latido reads from needs an OAuth app registered in that platform's developer portal. These guides tell you, per provider, how to get one and what to paste back into Latido.

Using your own keys ("bring your own keys"): open the guide for your provider, follow the checklist, and paste the credentials into Dashboard → Project → Providers → {provider}.

The capabilities below mirror Latido's provider catalog, the source of truth the API enforces (GET /v1/providers lists what your key can connect). Facts about each provider's portal come from research compiled on 2026-10-26 from the providers' public documentation, so form layouts can drift: when a portal differs from a guide, follow the portal.

#How to read the source tags

#The two URLs every provider app needs

The dashboard shows the exact values for each project and provider app. They follow these templates:

• https://api.getlatido.com is Latido's public API. It is public HTTPS, which every provider accepts (Oura and Withings refuse localhost and bare IPs).
• {slug} is the ProviderSlug value: garmin, strava, polar, suunto, coros, oura, whoop, withings, fitbit, google_health, wahoo, dexcom, huawei. Note the underscore in google_health (the guide file is google-health.md, the URL slug is not).
• {providerAppId} identifies the provider app inside Latido, so one backend can receive notifications for many customers' apps. You only know it after saving the app in the dashboard: save client id and secret first, then copy the webhook URL, then finish the provider's webhook form.
• Apple Health and Health Connect have neither: they are on-device stores, and data reaches Latido through POST /v1/members/{id}/ingest.

#Overview (October 2026)

"Managed app" means Latido's own approved app could serve every customer; "BYO keys only" means each customer must register their own app because the provider's terms forbid intermediaries or require one registration per end customer. Latido holds no approved managed apps today, so in practice every provider is BYO keys until that changes.

"None found" means this research found no AI clause, not that the provider's terms were reviewed line by line. Read the current agreement before shipping an AI feature on any provider's data. In Latido, providers with allowsAiProcessing: false (Strava, Oura) never reach MCP.

#Settings Latido asks for, per provider

Besides client id and client secret, some providers need extra values. They are stored encrypted (AES-256-GCM) in the provider app's settings. The keys below are the names the guides use; if the dashboard labels a field differently, the dashboard wins.

#Files

• One guide per provider: garmin, strava, polar, suunto, coros, oura, whoop, withings, fitbit, google-health, wahoo, dexcom, huawei, apple-health, health-connect.