How to Integrate the COROS API (2026)
Last verified October 17, 2026 · 5 min read
Sources checked (5) · October 17, 2026
- support.coros.com/hc/en-us/articles/53181619102996-Build-on-COROS-MCP — self-service MCP path, OAuth 2.0, single-user scope, limitations; read through the help center's article API
- support.coros.com/hc/en-us/articles/53181766856724-Partner-API-Access — Partner API requirements, capabilities, rate limit, application process, endpoint reference; read through the help center's article API
- support.coros.com/hc/en-us/articles/17085887816340-Submit-an-API-Application — EU data rules, standardized onboarding, how to apply; read through the help center's article API
- support.coros.com/hc/en-us/articles/50841795180948-Connect-Your-COROS-to-AI — data fields available through the MCP, FIT file cap, training plan rules; read through the help center's article API
- support.coros.com/api/v2/help_center/en-us/sections/53180979524884/articles.json — the same five articles with their publication and update dates, as JSON
COROS's help center, in articles published on September 2, 2026, describes two ways for an app to read COROS watch data: a self-service MCP endpoint that any developer can connect to over OAuth 2.0, one user at a time, and the Partner API for established platforms that need multi-user credentials, webhooks and two-way sync. Everything below is from COROS's help center articles on API access, read through the help center's public article API on October 17, 2026. If you are still choosing a provider, start with wearable data APIs.
COROS frames its approach around EU rules: it says it supports automated data sharing and API access for third-party platforms authorized by its users "in alignment with EU data protection regulations (including GDPR and the EU Data Act)", through a standardized, objective onboarding process rather than custom integrations or manual selection reviews.
Access: two paths#
| Build on COROS MCP | Partner API | |
|---|---|---|
| Who it is for | Developers building apps with COROS data | Established platforms needing multi-user access |
| Application | None: "No application or approval required" | Company details, technical contacts and OAuth 2.0 redirect URIs, plus acceptance of COROS's API Terms of Use |
| Users per authorization | One: access is scoped to the authorizing user only | Your whole user base, with multi-user OAuth 2.0 credentials |
| Webhooks | No, your app polls the MCP | Workout summary push within about 5 minutes, with retry logic |
| Two-way sync and routes | No two-way activity sync, no GPX routes | Two-way activity sync, structured workouts and training plans, GPX and KML routes up to 50MB |
| Rate limit | Not stated; FIT file requests are capped at 50 per day | 1,000 calls per minute |
The Partner API's requirements are an established platform with a demonstrated user base, a registered company with an authorized technical representative, standard security and data privacy compliance, and agreement to COROS's API Terms of Use. To apply, an authorized technical representative submits the application form and emails api@coros.com with company details, technical contacts and OAuth 2.0 redirect URIs; once COROS verifies your identity and security specifications it issues an API client ID and secret. COROS says that terms are standard and non-discriminatory, and that platforms not yet at that scale can build on the MCP and apply later.
The MCP path#
COROS's MCP server is at https://mcp.coros.com/mcp. You implement the OAuth 2.0 authorization flow pointing at it, add a "Connect COROS" button, and once the user logs in and authorizes your app you can read their training data and write workout plans through the MCP. COROS says any standard OAuth 2.0 client library will work and links full documentation in its COROS-MCP repository on GitHub.
The data available through the MCP, as COROS listed it in September 2026:
| Area | What COROS lists |
|---|---|
| Activities | Activity records, lap and segment data, workout feedback and training notes, and FIT files with GPS tracks, capped at 50 file requests per day |
| Health and daily data | Menstrual cycle data; daily steps, calories, workout duration and weekly Training Load; sleep; daily heart rate, HRV, stress, Wellness Checks and resting heart rate |
| Fitness | Current training plan and calendar, VO2 Max, Running Fitness, race prediction times, recovery status, threshold pace and pace zones |
| Profile | User profile and connected device information |
| Writes | Road running, trail running and cycling workouts and training plans that sync to the user's COROS library |
Two limits matter for analysis apps. Cycling power data is not part of the standard query set, so a power curve or FTP estimate is not possible from a basic query, and detailed GPS or split-by-split analysis needs the FIT files, which count against the 50-per-day cap. Training plans must be 4 to 16 weeks long, a plan or workout can be scheduled from today to 14 days out, and deleting one has to be done in the COROS app.
The Partner API#
COROS's Partner API reference groups its endpoints as follows:
| Category | Functions |
|---|---|
| Auth | OAuth 2.0: authorize, access token, refresh, deauthorize, bind state |
| User data | getUserInfo, getWorkoutRecords (30-day maximum range, 3-month lookback), getDailyData |
| Workout detail | getWorkoutDetailFit, a FIT file download |
| Push and webhooks | Workout summary push in about 5 minutes, with retry logic and your client ID and secret in the header |
| Training plans | tp/list/push, tp/workout/deleteById |
| Routes | route/push, GPX or KML up to 50MB |
| Workout upload | file/synchronous, file/upload (asynchronous) and file/upload/get for status |
The getWorkoutRecords limits shape any backfill: a request covers at most 30 days and reaches back at most three months, so a new partner connection cannot import a user's whole history through the API.
What changed recently#
| When | Change (COROS's help center) |
|---|---|
| September 2, 2026 | "Build on COROS MCP" and "Partner API Access" articles published, describing the self-service MCP path and the Partner API's requirements |
| September 21, 2026 | Workout and training plan creation through the MCP became available, per COROS |
| October 12, 2026 | "Partner API Access" last updated |
| October 20, 2026 | "Submit an API Application" last updated |
Gotchas and production notes#
- Pick the path by user count. The MCP is single-user per authorization and has no webhooks; serving many users with push and sync is what the Partner API is for.
- Poll gently on the MCP. With no webhooks, polling is the only way to see new data, and FIT files are capped at 50 requests per day.
- No power data in standard queries. Pull FIT files if you need cycling power.
- Short lookback on the Partner API. Workout records go back three months, in 30-day windows.
- Deletions happen in the app. Plans and workouts created through the MCP cannot be deleted through it.
The rest of the cluster is at how to integrate a fitness or health API.
Frequently asked questions
- Does the COROS API require approval?
- Not for the MCP path: COROS says building on its MCP needs no application or approval, only an OAuth 2.0 flow to https://mcp.coros.com/mcp. The Partner API does: you need an established platform with a demonstrated user base, a registered company with an authorized technical representative, and agreement to COROS's API Terms of Use.
- What data can I get from COROS?
- Through the MCP, COROS lists activity records, laps, workout feedback, FIT files with GPS tracks, daily steps, calories, Training Load, sleep, heart rate, HRV, stress, resting heart rate, menstrual cycle data, VO2 Max, race predictions, recovery status, pace zones and profile and device data. Cycling power is not in the standard query set.
- Does the COROS API have webhooks?
- Only the Partner API. It pushes workout summaries to your endpoint within about 5 minutes, with retry logic and your client ID and secret in the header. The self-service MCP path has no webhook push notifications, so an app built on it has to poll the MCP.
- What are the COROS API limits?
- The Partner API's rate limit is 1,000 calls per minute, and its workout records endpoint covers at most 30 days per request with a three-month lookback. On the MCP path, COROS caps FIT file requests at 50 per day; it publishes no general request limit for it.
- How do I apply for the COROS Partner API?
- Have an authorized technical representative submit COROS's API application form and email api@coros.com with your company details, technical contacts and OAuth 2.0 redirect URIs, then accept COROS's standard API Terms of Use. Once COROS verifies your identity and security specifications, it issues your API client ID and secret.
Keep reading
Elsewhere on the site
Pages that share this one’s concepts and sources, from other sections.
Next steps
Was this page useful?
Independent comparison, last reviewed October 17, 2026. Pricing, rate limits, and feature availability change often — confirm current details in each provider’s official documentation before you commit. Product and company names are trademarks of their respective owners; AIFitnessAPI is not affiliated with, endorsed by, or sponsored by any product listed here.
← All integration guides · by AIFitnessAPI