Amazfit (Zepp) data, in your own stack.
The Zepp app writes to Health Connect on Android and to Apple Health on iPhone, so Amazfit data reaches Open Health Sync through those uploads. There's no direct Zepp connector yet.
- Source
- Watches and bands
- How the data arrives
- Through Health Connect (Android) or Apple Health (iPhone), which the Zepp app writes to.
What it collects.
Each record maps to the same model as every other source, with the provider, source and device it came from.
- Steps
- Heart rate
- Sleep
- Workouts
- Calories
How it works.
- 01
Amazfit (Zepp) writes to Health Connect or Apple Health
On the phone, the Amazfit (Zepp) app shares its data with Health Connect or Apple Health.
- 02
Your app uploads it
Your app reads Health Connect or Apple Health and uploads it, as on the Health Connect or Apple Health page. Each record keeps Amazfit (Zepp) as its source.
- 03
You read one model
The records land in the same model as every other source, over REST, MCP and FHIR R4.
Before you start.
- Nothing to register with Zepp: the user turns on the Zepp app's Health Connect or Apple Health sync.
- Zepp Health also runs a partner Web API for approved companies, by application. There's no connector for it yet.
- Records that arrive through Health Connect keep Zepp as their source.
Where to start.
Amazfit (Zepp) has no connector of its own: set up the source its data goes through.
Questions.
Can I use Amazfit (Zepp) with Open Health Sync today?
Yes, through Health Connect or Apple Health, which your app uploads. There's no Amazfit (Zepp) connector of its own, and its records keep Amazfit (Zepp) as their source.
Do I need anything from Amazfit (Zepp)?
Nothing to register with Zepp: the user turns on the Zepp app's Health Connect or Apple Health sync.
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.