URL Parameters
Almost every parameter can also be passed in the launch URL, which is useful for standalone links and web embeds. A URL-only launch needs no postMessage at all: the app verifies from the URL parameters on its own. Applies to: All integrations.
Two URL modes:
1. Single encoded payload: ?data=<URL-safe base64 of a JSON object>. When it decodes, it is the entire URL payload: every other query parameter is ignored (except style, delegate, debug and themeName, which are also read straight from the URL). Values keep their JSON types, so send real booleans and numbers. Encode it with, for example: btoa(JSON.stringify(params)).replaceAll("+", "-").replaceAll("/", "_").replaceAll("=", "").
2. Individual parameters: ?userId=user-123&company=YOUR_COMPANY&key=YOUR_API_KEY&style=dark&showSilhouette=false. Empty values are skipped. Known booleans accept true, false, 1 or 0 (any letter case); known numbers are parsed as numbers; a value that starts with [ or { is parsed as JSON. Everything else stays text.
Precedence: values sent by postMessage override URL values (the URL acts as defaults), with these exceptions:
| URL Parameter | Equivalent Config | Example | Precedence |
| style | style | ?style=light | URL wins over postMessage |
| delegate | defaultDelegate | ?delegate=GPU | URL wins over postMessage |
| debug | showDebugRecording | ?debug=true | Combined with the postMessage value (either turns it on) |
Booleans read from individual URL parameters: isHideHeaderMain, isDrawingPose, hideFeelingDialog, hideOtherGender, hideConnectTvButton, legacyRestScreen, dynamicRestEnabled, includeRealtimeAccuracy, showSilhouette, showDebugRecording, showFormGuidance, streamFormGuidance, includePoseBorders, showLeaderboard, shouldAskCamera, shouldShowCameraSelector, showSettings, motionTrackingSettingOn, motionTrackingEnabled, selfModeEnabled, start_from_rest, nativeParentScroll, isHorizontalMode, customProfileAction, customCalendarAction, hideCalendarButton, hideProfileButton, showAiTrainerNameInHeader, captureDateOfBirth, includeFramingHints, includeFormState, enableGestureControl, frameExitPrompt, frameExitPause, isAssessment. Also accepted as text: pauseCamera, muteWorkout, showCommitScreen and boundedPoseWait ("true"), and isSubscribed ("false").
Numbers read from individual URL parameters: age, height, weight, countdown, reps, restDuration, minPoseDetectionConfidence, minTrackingConfidence, minPosePresenceConfidence, tugMinRequiredSpace, inactivityTimeout.
Every other boolean or number (for example shouldSendStats, disableCookies, disableGuide, autoSubmitLeaderboard, hideCompletionOverlay, hideStatisticsHeader, preventGestureControl, immediateShowSkip, shouldShowOpenCameraSettings, motionDataEnabled, gameTotalRounds): send it by postMessage or inside ?data=.
Lists and objects (exercises, restSpeeches, includePhrases, customWorkoutExercises, challenges_home, checkFrameText, planOnboardingPrefill, completed_exercises, fitness_goals, injuries, health_conditions, body_parts): as individual URL parameters they must be URL-encoded JSON, e.g. ?exercises=%5B%22model-id-1%22%5D for ["model-id-1"]. `includePoseData` also accepts a comma list: ?includePoseData=poseLandmarks,events.
Reloads: the launch query is kept for the browser tab, so a reload that drops it still launches with the same parameters.
Leaving a URL-only launch: with no host app to close the view, use exitUrl (Navigation) and, for the AI Trainer, subscriptionReturnUrl (AI Trainer parameters).