Examples

This page provides a minimal end-to-end sequence from token generation to SDK launch.

Backend: issue JWT

Your backend receives authenticated user context, creates a JWT signed with your private key, and returns that token through your secure API channel.

For the exact JWT contract, including supported algorithms and claim requirements, refer to Server-side Request Authentication.

Client: fetch launch payload

The client calls GetSessions to display available workouts, then calls GetSessionContent with the selected workout ID. The resulting session payload is kept in memory alongside the JWT and returned WorkoutKitToken for immediate launch.

Use the endpoint configured for the current client environment. Sandbox and production endpoints are provisioned per B2B client by the WorkoutKit team.

Launch SDK

On iOS, initialize GoModeController or GoVideoController with session content, token, and optional configuration. On Android, initialize GoFragment or WorkoutVideoFragment with the same inputs.

The recommended timing is to fetch the final session payload when the user has chosen the workout and is about to launch it. WorkoutKitToken is valid for 1 day, which is sufficient for a standard launch flow.

Completion handling

When a session ends, the host app listens for completion callbacks, stores session results, and forwards key events to analytics or backend services.

Contractual settings

Quota levels, rate limits, and SLA commitments depend on your contractual offer. Treat the values communicated during onboarding as the source of truth for production rollout.