Wahoo API integration
ELEMNT head units, RIVAL watches and KICKR trainers, behind one connect call — and the one provider on the platform that tells you exactly what the athlete agreed to share.
Live today for connections and activities. Three days free, then $20 a month, flat — no per-athlete fee.
All integrationslink a wahoo athlete — no wahoo credential involved
// Your own id for your own user. You hold no wahoo client secret.
const link = await stridee.post('/v1/connect', {
provider: 'wahoo',
external_user_id: 'user_4821',
return_uri: 'https://app.yourapp.com/settings/devices',
});
// Redirect their browser. Good for 30 minutes.
res.redirect(link.connect_url);Deliveries
What you get when a Wahoo workout finishes
An activity.created event carrying Wahoo’s own summary, sealed to your public key. The FIT file isn’t in it — that is a pre-signed provider URL that expires, because re-hosting your athletes’ activity files is a retention decision rather than something to slip into a webhook payload.
- Sport as Wahoo classified it, mapped onto one vocabulary
- Start time, duration and the Wahoo workout id
- The device — ELEMNT BOLT, RIVAL, KICKR
- The scopes the athlete actually granted, verbatim
Wahoo Cloud API
The Wahoo integration you’re not writing
Wahoo’s developer platform. You register an application, run OAuth2 against it and host a webhook — three things you do not do here.
Register an application, host a callback
The Wahoo Cloud API is a normal OAuth2 integration, which sounds fine until it is the fourth normal OAuth2 integration you are operating. Each one is a client secret in your environment, a redirect URI to keep in sync across environments, and a callback route in your router that is security-sensitive and rarely tested.
Subscribe to the right events, then keep them subscribed
Wahoo pushes workouts to a webhook you own, which means a public endpoint, signature checks, idempotency against retries and a story for what happens while you are deploying. That work is identical for every provider and it is not any part of what your product does.
Notice that Wahoo answers a question the others don’t
Wahoo reports what the athlete actually granted, so we pass it through verbatim rather than echoing the scopes we requested. COROS and Polar do not, and there we return null. Reconciling that difference is exactly the class of per-provider judgement call that makes six integrations cost far more than six times one.
What replaces all of it
One POST /v1/connect naming wahoo, and a webhook handler you write once for every provider. The registration is ours, the consent screen is ours, and the token refresh is ours.
Connecting a devicelink a wahoo athlete — no wahoo credential involved
// Your own id for your own user. You hold no wahoo client secret.
const link = await stridee.post('/v1/connect', {
provider: 'wahoo',
external_user_id: 'user_4821',
return_uri: 'https://app.yourapp.com/settings/devices',
});
// Redirect their browser. Good for 30 minutes.
res.redirect(link.connect_url);Coverage
What Wahoo does, and what it doesn’t yet
Nothing below is marked live unless an endpoint serves it today. Where Wahoo doesn’t send something, the field is absent rather than estimated — a null you can branch on is worth more than a number nobody measured.
- ConnectLive today
- ActivitiesLive today
- Daily summariesThe provider doesn’t expose it
- Workout pushDesigned, not yet shipped
Devices
Which Wahoo devices are covered
The integration is with the athlete’s Wahoo account rather than with a watch, so anything that syncs into it reaches you — including models released after you shipped, with no change on either side.
Cycling computers
- ELEMNT BOLT
- ELEMNT ROAM
- ELEMNT ACE
Watches
- RIVAL
Trainers
- KICKR
- KICKR CORE
- KICKR BIKE
Sensors
- TICKR heart rate
- RPM cadence
Pricing
Flat, and not per athlete.
A unified wearable API normally costs hundreds of dollars a month and meters every connected user on top — so the moment your product works, your bill grows with it. This is $20 a month for the whole API, whatever you connect.
$20
per month, flat
Every provider and every endpoint. Three days free first, and cancelling is a button in the Stripe billing portal.
No per-athlete fee
connect as many as you like
The bill is the same at ten connected athletes and at ten thousand. There is no credit balance to watch and no overage to model.
No approval queue
checkout is the signup
You are not applying to Wahoo Cloud API. Paying creates the account and opens the console, automatically, in the seconds it takes Stripe to tell us.
Three days free. Then $20 a month.
The private beta is open, and checkout is the whole signup — pay and your account exists, with the console switched on, before you have finished reading the receipt. No waitlist, no sales call, and nobody approving you.
- Keys the moment checkout finishes — no waitlist, no approval
- Garmin, COROS, Polar and Wahoo behind one connect call
- $20/month for the whole API — every provider, every endpoint
- One of only 50 founding slots, and the price they keep
- A private Discord channel with the engineers who wrote the integrations
- A vote on what we build next — the founding 50 order the roadmap
Cancel in one click from the billing portal, at any point in the three days or any month after. If something goes wrong on our side, email hi@stridee.fit and we refund you. No forms, no conditions.
Founding slots
50
Only 50 founding slots exist. When they are gone, they are gone.
Card required, nothing charged for three days. Flat rate for the whole API, not per connected athlete.
Start building — free for 3 daysStripe checkout · cancel any time · keys the moment it clears
What happens next
You pay
Stripe collects the card. Three days free first, then $20/month, and cancelling is a button in the same billing portal.
We create your account
Against the email you paid with, automatically, the moment Stripe confirms. Nobody reviews it.
You log in
platform.stridee.fit/login, same email, code in your inbox. Mint a signing key and your first call works.
Already bought and want the console? platform.stridee.fit/login
Not ready to claim?
Come talk to us in Discord first. We answer questions there before anywhere else.
Join the Discord
Join the DiscordWahoo API questions
No. That is the point of the integration. We hold the Wahoo Cloud API 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 Wahoo secret in your environment, no callback route in your router, and no approval queue between you and your first connected athlete.
Three days free, then $20 a month, flat — for the whole API, every provider and every endpoint, with no per-athlete metering. 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. Cancel from the Stripe billing portal whenever; access ends when the period does.
You get push, not polling. When an athlete finishes a workout, Wahoo 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 Wahoo 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.
Yes — anything that lands in the athlete’s Wahoo account reaches you, whether it was recorded on an ELEMNT head unit outdoors, a RIVAL watch or a KICKR trainer indoors. The delivery names the device, so you can tell them apart without guessing from the data.
On Wahoo, yes, and verbatim — it is the only provider on the platform that reports it, so a connection’s scope field is populated rather than null. On COROS and Polar we return null instead of filling the field with the scopes we requested, because inventing that answer is worse than admitting we do not have it.
The full documentation is public and needs no account. Still have questions? Ask us in Discord
Other integrations
One integration, not six
Every provider below is the same connect call, the same event shape and the same $20 a month. Adding your second one is a string change.
Live today
