COROS API Integration Guide 2026: Partner Access
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

You can integrate COROS watch data through the COROS API, but the full route is the COROS Partner API, and COROS only admits established platforms with a demonstrated user base. If you qualify, you get multi-user OAuth, workout push and FIT file downloads. If you do not, COROS points you to its self-service MCP server, which was built for one person connecting an AI tool to their own account. No price for the Partner API is published. The rule that decides most projects is simple: if you cannot show COROS an existing user base, plan on an aggregator or wait.
A note on sources. We read the COROS Partner API facts on COROS's own support pages, "Submit an API Application" and "Partner API Access", on 10 November 2026. We read the MCP facts on a coros.com page, and the Terra polling facts on Terra's own docs.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
COROS integration at a glance
| Question | Short answer |
|---|---|
| Official API? | Yes, a Partner API by application. API docs are private and shared after you apply (COROS shares the API reference after you apply, and Nango states the docs are private). |
| Cost to developer? | Not published. COROS calls its terms "standard and non-discriminatory". |
| Does the end user need a subscription or device? | They need a COROS watch and a COROS account. No paid user subscription is mentioned for the API. COROS says the MCP may need a paid plan on the AI tool side. |
| Same-day start? | Only on the MCP route, which is self-service. The Partner API needs review first. |
| Who approves scale-up? | COROS, after identity and security checks. Waiting time not published. |
| HIPAA / BAA? | Not published. Nothing on COROS pages mentions HIPAA or a BAA. |
| Raw vs summary data? | Workout summaries plus FIT files with samples. The Partner API lists a getDailyData call for daily health data. Which daily fields it returns is not published. |
| First build | About 4 to 5 weeks after approval. This is our estimate. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Data latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Partner API (cloud REST + webhooks) | No | Yes | Yes, application and API Terms of Use | No | Workout push about 5 minutes after a workout | Workout summaries, FIT files, daily health data (getDailyData), two-way sync, training plan push, GPX or KML routes up to 50MB | Workout records come in windows of 30 days at most, going back 3 months | Established platforms with users already on COROS |
| COROS MCP server | No | No for personal use | No, self-service | No | On request, no push | Workouts, FIT files, daily steps, sleep, HR, HRV, stress, resting HR, training load, menstrual cycle, profile (coros.com) | No push. 50 FIT files per user in a 24-hour window. Each user authorizes only their own data | AI tools and early apps that can poll. Not a fit when you need push |
| Aggregators, checked 10 November 2026 | Terra lists COROS as a cloud source and polls each account about every 15 minutes. Spike lists it with no route stated. Junction and ROOK do not list it. Thryve, Validic and Sahha coverage is not published. Nango also connects to COROS. | |||||||
| Apple Health / HealthKit | Yes | Optional | No | HealthKit | After phone sync | Types the user picks in COROS settings: cycling distance, heart rate, sleep analysis, steps, swimming distance, and walking and running distance (COROS support, read 11 Nov 2026). Resting heart rate during sleep was added in July 2025. | Not published | iPhone apps that already read HealthKit |
| Health Connect | Yes | Optional | No | Health Connect | Not published | COROS product pages say it is supported. Data types are not published. | Not published | Test before you plan on it |
| File export by the user | No | Yes, to receive files | No | No | Manual | One workout as FIT or GPX from the app. Full workout history as FIT or TCX from COROS Training Hub, sent by email. | Daily data such as heart rate and steps cannot be exported. Sleep and daily data only by a support request for a date range. | One-off history loads for a study or a new patient |
For a healthcare buyer such as a cardiac rehab or sports medicine program: apply for the Partner API if you already have users, and ask COROS in writing about health data and HIPAA before you sign. If you are new, start with an aggregator. For a consumer fitness or coaching app: the Partner API is the right target once you have traction, because it gives you FIT files and push. COROS now lets developers build apps on the MCP route with OAuth 2.0 and no application. Each user connects only their own account, and there is no push, no GPX routes and no two-way activity sync.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose COROS API access? | Yours. You apply as an established platform. | The aggregator's | Yours. We prepare the application with you. |
| Can a new product start? | Only on the MCP route, with no push, until COROS accepts you | Yes, if the aggregator lists COROS | Yes. We start on MCP or an aggregator and plan the Partner API move. |
| API terms risk | Your counsel reads them. They are shared only after you apply. | Covered by the aggregator's own terms with COROS. Not published. | Your counsel reads them. We design storage around the answer. |
| Webhooks, FIT parsing and token renewal | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | COROS fields and FIT files | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | COROS review time, not published, plus your build | Depends on the aggregator's onboarding | About 4 to 5 weeks of build after approval in our estimate, see the Delivery timeline |
| Cost shape | Engineering time. The Partner API fee is not published. | Aggregator fee | Project fee, scoped after a call |
What data you can get
| Data type | Granularity | History window | Push or pull |
|---|---|---|---|
| Workout summary | Per workout | Not published | Push, about 5 minutes after the workout, with retries |
| Workout detail (FIT file) | Sample level: GPS, heart rate, laps | Not published | Pull via a workout detail endpoint |
| Daily steps, calories, sleep, HR, HRV, stress, resting HR | Daily, plus some time series | Not published | MCP on request (coros.com). Partner API lists getDailyData, but its field list is not published |
| VO2max, training load, recovery status, race predictions | Summary | Not published | MCP only (coros.com) |
| Menstrual cycle | Not published | Not published | MCP only (coros.com) |
What is inside one COROS lap record
The Partner API field list is private, so this is the richest record COROS publishes: the lap data from its MCP Tool Guide. One record per lap or segment, with these fields in the example.
| Fields | What they hold |
|---|---|
| lapIndex, distance, time | Lap number, lap distance and lap time |
| avgHr, maxHr | Average and peak heart rate for the lap |
| avgPace, adjustedPace, avgSpeedV2, vertSpeed | Pace, adjusted pace, speed and vertical speed |
| avgPower, formPower, legStiffness | Running power fields |
| avgCadence, maxCadence, avgStrideLength, strideRatio, strideHeight, groundTime, groundBalance | Running form |
| elevGain, totalDescent | Climb and descent |
| bodyTemperature | Present in the example with a value of 0 |
Units for these lap fields are not published. Fields depend on the device, sport and recorded data. You can also ask for any time window inside one activity, with start and end as Unix timestamps in seconds. Sleep comes as a score, main sleep, deep, light and REM ratios, awake time and naps. HRV comes in milliseconds, with a COROS normal range and a sleep HRV time series where available.
What you cannot get
- Public API documentation. You see it only after you apply.
- The field list for the Partner API daily data call. COROS lists getDailyData, but does not publish whether it includes heart rate, HRV, sleep or SpO2.
- Workout history older than 3 months. The workout records call looks back 3 months, in windows of 30 days at most.
- SpO2 on the Partner API. It is not published. On the MCP route, the wellness check returns SpO2 and respiration rate, but only for the latest complete check.
- Webhooks on the MCP route. Your app must ask for data.
- More than 50 FIT files a day per account on the MCP route.
- Published OAuth scopes. Token lifetimes are published only for the MCP route.
- Any statement on medical use, HIPAA, a BAA, FDA status or data residency.
How to get access
- Check you meet the bar: an established platform with a demonstrated user base, a registered company, and an authorized technical representative.
- Email api@coros.com with your platform details.
- Submit the API application form linked from COROS support article 17085887816340.
- Agree to the COROS API Terms of Use, which cover security, data privacy and rate limits.
- COROS runs identity and security checks, then issues a Client ID and Secret. Who reviews and how long it takes is not published.
- If you do not qualify, the MCP server at https://mcp.coros.com/mcp is open to anyone with a COROS account. COROS also lets developers build on it with OAuth 2.0, one user per authorization, but with no push. Teams that need push use an aggregator and reapply once they have users.
From zero to your first COROS data in four steps
- Pick the route. With an established user base, email api@coros.com with your company details, technical contacts and OAuth 2.0 redirect URIs, and submit the application form. Without one, start on the MCP route, which needs no application.
- Add OAuth 2.0. COROS says any standard OAuth 2.0 client library works. On the MCP route the access token lasts 30 days and the refresh token 180 days, and each refresh issues a new refresh token, so store the new one every time. Partner API token rules are not published.
- Make a first call. COROS does not publish a raw HTTP request. Its Tool Guide gives the tool, the parameters and a response. Dates use yyyyMMdd in the account's timezone, and a night of sleep belongs to the date you wake up.
Tool: querySleepOverview Arguments: {"startDate": "20261015"} Sleep Overview 2026-10-15 Sleep Score: 91 Daily Sleep: 7h 57min (incl. naps) Deep Sleep Ratio: 27% Light Sleep Ratio: 41% REM Ratio: 31% Awake Time: 5 min - Load history, then keep up. On the Partner API, pull workout records in windows of 30 days at most, back 3 months, then take the workout push. On the MCP route, poll by date range. HRV, wellness check and stress time series queries cover at most 7 days per call.
Terms you must know
We could not read the COROS API Terms of Use. They are part of the private application. What follows is what is public and what you must ask for.
- Medical use: not published. For a healthcare product, get written permission before you use COROS data in care decisions. For a wellness product, the risk is lower but still unknown.
- PHI and HIPAA: not published. Once workout data sits in a patient record, it becomes PHI on your side. COROS has said nothing about how it treats that.
- BAA: not published. A covered entity should ask whether COROS will sign one. Until you have a yes in writing, plan as if the answer is no.
- Storage and retention: not published. Ask how long you may keep data and what happens when a user disconnects.
- AI training: not published for the API. The MCP route exists to feed an AI assistant, so users can send their own data to AI tools. That tells you nothing about what a partner may do.
- Display and branding: not published. Ask for the rules before you design screens.
- Data selling: not published. Assume it is banned and confirm.
- Termination: not published. Ask how much notice you get and what you must delete.
- Competing products: not published. A training platform that competes with COROS's own app should ask directly.
- Security and privacy compliance: COROS requires "standard security requirements" and "data privacy compliance". The standard itself is not named.
Cost and payment terms
- Developer fee for the Partner API: not published.
- Terms are described as "standard and non-discriminatory".
- End users need a COROS watch. No paid COROS subscription is mentioned for API access.
- MCP route: free on the COROS side. COROS says you likely need a paid plan on the AI platform side to use MCP.
- Aggregator fees: not published. Ask Terra or Nango for a quote.
Use cases
Cardiac rehab and exercise prescription
The patient links COROS through your web portal with OAuth. When they finish a session, COROS pushes the workout summary to your server. You fetch the FIT file, pull heart rate and duration, and write FHIR Observations to the EHR so the care team sees exercise done against the plan. Data used: workout duration, heart rate samples, distance.
- COROS rejects your application because you have no user base. Fix: start through an aggregator and reapply later.
- The push arrives before the detail is ready. Fix: retry the FIT download with backoff and treat the first message as a summary only.
- Heart rate is wrist-based and not cleared for clinical use. Fix: show it as patient-generated data, not as a vital sign.
Clinical trial activity endpoints
Participants wear COROS watches in a study. Your server receives each workout, stores the FIT file as source data and computes the endpoint, such as weekly minutes of exercise. Data used: workout summaries and FIT samples.
- The daily data call exists, but its fields are not published. Fix: ask COROS during review which daily fields getDailyData returns before you promise them to clinicians.
- Participants forget to sync the watch. Fix: alert the site when no workout arrives in a set number of days.
- History window is unknown, so backfill may fail. Fix: connect participants at enrollment, not later.
Endurance coaching app
The athlete connects COROS in your app. Workouts flow in by push. Your coaches build plans and send workouts back to the watch through the training plan push call (tp/list/push). Data used: workouts, FIT files.
- Laps on structured workouts may arrive as one lap (Terra docs). Fix: rebuild splits from distance and pace samples.
- Duplicate deliveries. Fix: upsert on the workout ID.
Employer wellness challenge
Employees link COROS alongside other brands. You count workouts and minutes per person per week and show a leaderboard. Data used: workout summaries.
- Small program size fails the COROS bar. Fix: use an aggregator that already supports COROS.
- Aggregator polling adds up to about 15 minutes of delay (Terra). Fix: do not promise real-time scores.
COROS data in an EHR or remote monitoring program
Most healthcare teams want COROS readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Ask COROS about medical use first, because its terms on that are not published.
| COROS value | FHIR Observation | Code |
|---|---|---|
| Daily average heart rate, or workout heart rate from the FIT file | Heart rate, beats per minute | LOINC 8867-4 |
| Resting heart rate | Resting heart rate, beats per minute | LOINC 40443-4 |
| Wellness check SpO2 | Oxygen saturation by pulse oximetry, percent | LOINC 2708-6, plus 59408-5 for pulse oximetry |
| Wellness check respiration rate | Respiratory rate | LOINC 9279-1 |
| Daily steps | Step count | LOINC 55423-8 |
| Main sleep duration | Sleep duration | LOINC 93832-4 |
| Workout duration and calories | Exercise duration, calories burned | LOINC 55411-3 and 41981-2 |
| HRV, stress, training load, recovery | Device-specific Observation | Your own code system. COROS gives HRV in milliseconds but does not say which HRV method it uses, and the other scores are COROS's own. |
Keep the COROS activity id (labelId) and sport code on each Observation, so a later push for the same workout updates it instead of making a copy.
Known blockers and gotchas
- User-base bar. COROS only admits established platforms. Have user numbers and a company profile ready before you email.
- Private docs. You cannot scope the build until COROS shares the docs. Budget your estimate only after access.
- Conflicting webhook reports. The COROS Partner API Access page (read 10 November 2026) says partners get workout push within about 5 minutes. Terra says COROS does not provide webhooks to third-party integrators and polls each account about every 15 minutes. The two may describe different kinds of access. We cannot tell which from public pages. Ask COROS which applies to you.
- Summary before detail. Terra reports a first delivery can hold only the summary, with samples and laps arriving later under the same ID. Upsert and keep the latest.
- MCP is a thin product backend. It has no push, a cap of 50 FIT files per user in a 24-hour window, and health queries that cover at most 7 days per call.
Delivery timeline
Our estimate. Steps marked "vendor" depend on COROS.
| Week | Work | Depends on vendor? |
|---|---|---|
| 0 to ? | Application, identity and security review, docs shared | Yes. Time not published |
| 1 to 2 | OAuth flow and webhook receiver | No |
| 3 to 4 | FIT parsing and FHIR mapping | No |
| 5 | Testing with real watches | No |
About 4 to 5 weeks of build after approval. Through an aggregator, skip the vendor wait.
Questions to ask COROS before you sign
- What user base counts as "established", and how long does review take?
- Which fields does getDailyData return: heart rate, HRV, sleep, SpO2?
- Will our account get workout webhooks, or must we poll?
- Do your API terms allow use in a clinical or medical product?
- Will you sign a BAA, and where is data stored?
- Is there a fee now, and how much notice before one starts?
- How far back can we pull history when a user first connects?
- What are the OAuth scopes, token lifetimes and refresh rules?
Other device integration guides
COROS is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- Polar API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Ready to build with COROS data?
Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. We do not have an existing COROS partnership, so the plan covers your application to COROS too. Book a call about your device integration.
For whoever builds this
- Auth: OAuth 2.0 on both routes. Partner API scopes, token lifetime and refresh rules not published. Nango notes COROS lists no OAuth scopes.
- Rate limit: 1,000 calls per minute on the Partner API. MCP: 50 FIT files per platform user in a fixed 24-hour window, shared by file downloads and download links.
- Webhook: workout summary pushed about 5 minutes after the workout, with retries, client credentials in the header. Signing method not published.
- FIT: download via the workout detail endpoint. Endpoint path not public.
- MCP endpoint: https://mcp.coros.com/mcp. It routes to your account region. Regional URLs remain for clients that do not follow redirects: mcpus.coros.com, mcpeu.coros.com and mcpcn.coros.com. COROS added create and edit access for training plans and workouts in a September 2026 update (coros.com).
- Terra: upsert on summary_id. To get current state call GET /v2/activity with with_samples=true and to_webhook=false.
- FHIR mapping (our mapping, codes checked on the NLM LOINC search 11 Nov 2026): heart rate LOINC 8867-4, steps 55423-8, exercise duration 55411-3, calories burned 41981-2. 55430-3 is walking distance by pedometer, so use it for walks only and a local code for GPS run, ride or swim distance.
- MCP limits beyond FIT: the AI cannot delete plans or workouts (coros.com).
- MCP data list (coros.com): workout records, summaries, split and lap data, athlete notes, FIT files, VO2max, running power, threshold pace, race predictions, training load, volume, recovery status, training schedule, daily steps, calories, sleep, heart rate, HRV, stress, resting heart rate, menstrual cycle, time-series stress, quick health check, sleep HRV, profile and bound devices.
- COROS and Wahoo announced a data partnership (coros.com press release). It does not open a public API for other developers.
- Version and sunset dates: not published.
Sources
All read 10 November 2026.
- COROS and Apple Health, https://support.coros.com/hc/en-us/articles/360041549551-Connecting-Apple-Health-with-COROS-App, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
- Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- https://support.coros.com/hc/en-us/articles/17085887816340-Submit-an-API-Application (read in a browser, 10 November 2026)
- https://support.coros.com/hc/en-us/articles/53181766856724 (read in a browser, 10 November 2026)
- https://coros.com/au/stories/coros-metrics/c/mcp-testing (COROS MCP page, read directly)
- https://coros.com/ca/stories/press-release/c/coros-wahoo-partnership
- https://docs.tryterra.co/faq/help-topics/data-api-sdk/webhooks-dedup-and-sync-reliability/coros-polling-latency-no-webhooks (third party)
- https://nango.dev/docs/integrations/all/coros (third party)
- https://tryterra.co/integrations/coros (third party)
- COROS Partner API Access, https://support.coros.com/hc/en-us/articles/53181766856724, read 11 November 2026.
- COROS Build on COROS MCP, https://support.coros.com/hc/en-us/articles/53181619102996, read 11 November 2026.
- COROS Connect Your COROS to AI, https://support.coros.com/hc/en-us/articles/50841795180948, read 11 November 2026.
- COROS export articles 360043975752, 33125636125204 and 25002333092500 on support.coros.com, read 11 November 2026.
- COROS MCP README, Tool Guide and FAQ, https://github.com/coroslab/COROS-MCP, read 11 November 2026.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does COROS have a public API?
How do I apply for the COROS API?
How much does the COROS API cost?
Can a new startup get COROS API access?
Does the COROS API support webhooks?
Can I get sleep and HRV from COROS?
Can I download FIT files from COROS?
Is COROS HIPAA compliant or will it sign a BAA?
What is the COROS API rate limit?
Can I use the COROS MCP server to build a product?
How long do COROS OAuth tokens last?
How much history can I pull when a user first connects?
Can I get SpO2 from COROS?
What units and dates does COROS use?
Which OAuth calls does the COROS Partner API have?
Can a patient export their own COROS data?


