Coros is on the roadmap.
Coros is planned, over its cloud API with OAuth. Partner access comes from COROS directly.
- Source
- Sports watches
- How the data arrives
- Cloud API, OAuth 2.0; a partner API with webhooks for established platforms.
What it would collect.
What Coros offers developers, as listed in the connectors table. The final connector may cover less.
- Activities
- Health metrics
- Fitness assessments
How it would work.
Once the connector is built, the same way every other source works today.
- 01
The user connects
Your server asks for a consent URL and sends the user to Coros. Tokens are stored encrypted.
- 02
The server pulls
A first backfill, then scheduled pulls, and webhooks where the provider sends them. Every raw payload is kept.
- 03
You read one model
Units, time zones and duplicates handled, served over REST, the read-only MCP server and FHIR R4.
Before you start.
- Partner access is requested from COROS, and the full docs are shared after registration.
Want it sooner?
Connectors are self-contained: one package that maps a provider into the same model. Tests use recorded fixtures and a fake of the provider's API, so no real account is needed to build one.
Questions.
Can I use Coros with Open Health Sync today?
Not yet. Coros is on the roadmap and no code for it runs today. The planned path: Cloud API, OAuth 2.0; a partner API with webhooks for established platforms.
Do I need anything from Coros?
Partner access is requested from COROS, and the full docs are shared after registration.
Where does the data go?
Only to the server you run. Open Health Sync is self-hosted software, not a service: no account with us and no call home. Each user can be deleted with one call, raw files included.
How can I get it sooner?
Connectors are self-contained. The guide on writing a connector walks through one, and an issue on GitHub tells the maintainers it matters to you.