Zwift
Zwift is a Long Beach, California online fitness company that operates a multiplayer indoor cycling and running platform combining stationary smart trainers and bikes with a 3D virtual-world game client. Riders and runners use a smart trainer, smart bike (such as the in-house Zwift Ride), treadmill, or pod to drive an avatar through fictional worlds (Watopia, Makuri Islands) and licensed real-world routes, joining structured workouts, group rides, races, training plans, and 24/7 events alongside a global community of more than a million members. The platform pairs with smart trainers and heart-rate monitors over Bluetooth and ANT+, and the Zwift Companion mobile app provides in-game messaging, ride control, and route discovery. Zwift does not operate a general public developer portal, OpenAPI reference, or open-source SDK. Its developer surface is limited to a private, application-only Structured Training API for approved training partners (TrainingPeaks, TrainerRoad, Wahoo SYSTM, JOIN Cycling and similar coaching platforms) that lets external workout builders push custom workouts into a rider's Zwift account, plus one-way activity-export connections to Strava, TrainingPeaks, Garmin Connect, MapMyRide, MapMyRun, Adidas Running, Technogym, Fitbit, Wahoo, Apple Health, and Withings. There is no public REST surface, OAuth client registration, or partner self-service available to general developers — third-party tools (community libraries, ZwiftPower, Sauce for Zwift) interact with Zwift via reverse-engineered private endpoints, not a sanctioned API. Zwift is a paid consumer subscription business; revenue comes from monthly memberships and hardware sales (Zwift Ride, Zwift Cog, Zwift Click, Zwift Play).
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Zwift the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zwift scores 14.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Zwift
Each block below is one kind of artifact we hold for Zwift. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Zwift — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 4
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 14
Properties that don't map to a standard resource type
Scroll within the panel for all 14 ·
← All providers · Data indexed from github.com/api-evangelist/zwift · machine-readable index on apis.io