The Huawei watch your user already wears, behind the same connect call as every watch we support. They sign in with their HUAWEI ID once on a screen we host, and their workouts, sleep and daily activity start arriving.
Stripe gave you every payment method with one integration. Stridee gives you every watch.
From $32.50 a month billed annually.
your huawei user finishes a session — this is all you write
// decrypt() and stridee() are in /docs
export async function onStrideeEvent(rawBody, res) {
const event = await decrypt(rawBody);
if (event.type === 'activity.created' && event.data.file) {
// event.data.device → "Huawei"
// A FIT file, written by us from Huawei’s summary.
const file = await stridee('GET', event.data.file.url);
await saveActivity(event.user_id, file);
}
res.json({ nonce: event.nonce });
}Health Service Kit is closed to individual developers. Huawei verifies the company, then reviews a written application for every data type you ask for, with a usage table per scope and a document introducing the business. That takes about ten working days, and until it clears the app is capped at 100 members. Through us it is a string in a connect call.
Huawei’s consent screen is a list of checkboxes, one per data type, and a member may tick sleep and leave heart rate. Every read of an unticked type is a 403, and so is every read for a member who has not switched on data sharing inside the Huawei Health app. Neither means the connection is dead, so each one has to be told apart from a token that really has expired.
Workouts are queried in milliseconds, sleep records in nanoseconds, daily totals by calendar date in the member’s time zone, and no window may be wider than a month. A sleep record’s stage durations carry no unit at all. We normalise the lot and send you one record with seconds in it.
All of it is one POST /v1/connect naming huawei, and a webhook handler you write once for every provider.
Connect a deviceyour huawei user finishes a session — this is all you write
// decrypt() and stridee() are in /docs
export async function onStrideeEvent(rawBody, res) {
const event = await decrypt(rawBody);
if (event.type === 'activity.created' && event.data.file) {
// event.data.device → "Huawei"
// A FIT file, written by us from Huawei’s summary.
const file = await stridee('GET', event.data.file.url);
await saveActivity(event.user_id, file);
}
res.json({ nonce: event.nonce });
}Checkout is the signup. No waitlist, no sales call.
Cancel any time from the Stripe billing portal, or email [email protected].
Plans start at
Or $39/month, month to month. Paying annually gets you two months free.
Hacker, Startup, Scale and Enterprise differ on how many of your users may connect a watch. The API is the same on every plan.
See the plans14-day free trial · cancel any time
We create the account on the email you pay with, automatically. Sign in at platform.stridee.com/login. Nothing to wait for.
No. That is the point of the integration. We hold the HUAWEI Health Service Kit registration, the client credentials and the redirect URI; you call POST /v1/connect with your own id for your own user and redirect their browser to the URL that comes back. There is no Huawei secret in your environment, no callback route in your router, and no Huawei company review of your own. Huawei does cap how many members one app may connect until its own review of that app clears, so tell us ahead of a large launch.
Two weeks free, then from $32.50 a month billed annually — or $39 a month with no year to commit to — for the whole API, every provider and every endpoint, with no charge for calls. What separates the plans is how many of your users may connect a watch. Hacker is up to 100, for a project and its first users; Startup covers up to 500; Scale includes 1,500 and bills the ones past that at a published per-user rate, with no ceiling; Enterprise is a contract with a better rate again; and none of them charges for calls, activities or endpoints. The usual price for a unified wearable API starts in the hundreds of dollars a month and charges again for each connected user, which is a pricing model that punishes exactly the thing you are trying to do. Cancelling is a button in the Stripe billing portal; access ends when the period does.
You get push, not polling. When an athlete finishes a workout, Huawei notifies us and we send you an activity.created delivery — sealed to your public key as a JWE and signed with a detached JWS you verify against our published JWKS. Latency is whatever Huawei takes to process the upload from the watch, which is theirs to own and typically a matter of minutes. You never write a polling loop and never hold a rate-limit budget.
There is no API key anywhere in this, in either direction. You authenticate to us with an Ed25519 signature over the request itself — RFC 9421 HTTP Message Signatures — using a private key that never leaves your machine, so there is no bearer token sitting in a log line, a CI variable or a backup. And we never hand you the provider's own credentials either.
Every watch and band that syncs to the Huawei Health app, because the integration is with the HUAWEI ID rather than with a watch. The WATCH GT, WATCH FIT, WATCH and Band lines all reach you the same way, and a model released next year works on the day it ships. The device on a delivery reads “Huawei”: the API does not say which watch it was.
The two days before they connect, today. Huawei shows an app only the data created after a member authorises it, unless Huawei has granted that app its separate history permission, which reaches back one year. Ours is under review. When it is granted, connecting replays up to a year of workouts, sleep and daily activity into your event stream as ordinary deliveries, with no second code path on your side.
Yes, and it is one we write. Huawei’s cloud API exports no workout file: it returns an activity record with a summary, so we write that summary into a FIT file and a Huawei workout arrives in the same shape as everyone else’s. It holds the sport, start time and duration, distance, energy, ascent, and average and maximum heart rate. It holds no GPS track and no per-second samples.
One wellness record per sleep, and a nap is its own record. Each carries the time in deep, light, REM and awake and Huawei’s own sleep score. A daily record carries steps, distance, and average, maximum, minimum and resting heart rate. HRV, stress, SpO₂, skin temperature and weight are not delivered yet: our side is written and is switched on once Huawei grants our app those permissions. A member chooses which data types to share on Huawei’s consent screen, so a record only carries what they ticked.
When the watch has synced to the phone and the phone to Huawei’s cloud, which is the honest bound and is not ours. Huawei notifies us when a member has new data and we fetch it then; we also re-read each member’s last three days every four hours, which is what Huawei recommends beside notifications. A workout typically follows the sync by minutes. Sleep and heart rate reach Huawei’s cloud more slowly, on a scale of hours.
Not yet. Huawei has a course import that puts a planned run, walk or hike on the watch, and our side of it is written; it is switched on once Huawei grants our app the permission, which is why the table above marks workout push as planned rather than unavailable. Until then a workout call naming this provider is answered as unsupported rather than half-working.
Everywhere Huawei offers its cloud API, which is not everywhere a Huawei watch is sold. Huawei does not serve the server-side API to accounts in Russia, so a member there cannot connect. Everyone else signs in with the HUAWEI ID they already use in the Huawei Health app.
The full documentation is public and needs no account. Still have questions? Ask us in Discord