COROS: register your app (Partner API)

There is no public API reference: COROS shares the spec with partners after approval. Everything about hosts, paths and token lifetimes below is UNVERIFIED until you have it.

#Steps

1. Read the Partner API Access page, https://support.coros.com/hc/en-us/articles/53181766856724 (updated 2026-09-03) [OFF].
2. Apply through the application form linked there and email api@coros.com [OFF]: company, product, user base, which data you need (workouts, daily data, FIT files) and whether you will push training plans.
3. If you are a small builder without a user base, COROS offers a self-service "Build on COROS MCP" OAuth instead [OFF]. It is not the partner API Latido's adapter targets.
4. After approval, COROS gives you a client id, client secret, the spec and a sandbox host [OFF/2ND]. Register the redirect URI https://api.getlatido.com/connect/callback/coros and the workout-summary push URL https://api.getlatido.com/providers/coros/webhook/{providerAppId} (how they are registered, portal or email, is UNVERIFIED).
5. In Latido, Providers → COROS → Custom app: paste client id and secret. No extra setting: COROS sends your client id and secret in the push request headers, and Latido compares them [OFF].

#Scopes

Not published [2ND].

#Gotchas

• Workout records: 30-day max per query, 3-month lookback [OFF]. Latido's backfill is capped at 30 days for COROS.
• Pushes arrive about 5 minutes after the watch syncs, with retries [OFF].
• Rate limit 1,000 calls/minute [OFF].

#Sources

• https://support.coros.com/hc/en-us/articles/53181766856724
• https://forum.intervals.icu/t/coros-support-added/37006?page=4 [2ND]
• https://nango.dev/docs/integrations/all/coros.md [2ND]