Shared query parameters (Tracking + Upload Tracking)

Parameters shared by both endpoints, with endpoint-specific differences.

Both endpoints use query parameters to control behavior.

Endpoints:

• Tracking (camera/webcam):

https://app.posetracker.com/pose_tracker/tracking

• Upload Tracking (video/image):

https://app.posetracker.com/pose_tracker/upload_tracking

Use this page as the single reference for parameters that exist on both.

token (required)

Your PoseTracker API key.

• Applies to both endpoints.

• Without it, the page shows an in-page error.

Related docs:

• Tracking: Tracking Endpoint params

• Upload: Upload Tracking – Query parameters

exercise (optional)

Selects the movement to track and analyze.

• Tracking endpoint: enables rep counting and posture states.

• Upload Tracking: video only.

If omitted:

• Tracking endpoint still runs pose estimation.

• Upload Tracking can still draw the overlay.

difficulty (optional)

Controls thresholds for counting reps.

Values:

• easy

• normal

• pro

Defaults can differ by endpoint.

skeleton (optional)

Controls the skeleton overlay.

• Upload Tracking: skeleton=true|false.

• Tracking endpoint: can also accept a custom skeleton UUID.

keypoints (optional, plan-gated)

Enables keypoints output to the host app.

Values:

• true

• false

Plan gating:

• Not available on Free.

• Allowed on Developer / Custom / Company.

See Plan restrictions.

angles (optional, plan-gated)

Enables computed angles output.

Values:

• true

• false

blazepose (optional, plan-gated)

Switches pose model from MoveNet to BlazePose.

Values:

• true

• false

BlazePose is heavier. Real-time can be slower on phones.

width / height (optional)

Controls the embed layout.

• Tracking endpoint: size of the camera container.

• Upload Tracking: size of the media container.

Message payloads

Parameters above change which messages you receive.

• Tracking endpoint messages: Tracking Endpoint Message to handle

• Upload Tracking messages: WebView / native messages