PoseTracker integration

Choose the best integration approach for your product.

Solution 1: Tracking WebViews / iframes (recommended)

Tracking WebViews / iframes is the simplest way to integrate PoseTracker. You embed a PoseTracker URL inside an iframe (web) or WebView (mobile). PoseTracker handles:

• camera access (real-time)

• pose estimation (V3 engine)

• exercise tracking (reps / duration / custom)

• optional overlays and developer outputs (keypoints / angles / recommendations / progression)

Official V3 entrypoints

Real-time (webcam / camera)

GET https://app.posetracker.com/pose_tracker/tracking?token=...&exercise=...

Upload (video or image)

GET https://app.posetracker.com/pose_tracker/upload_tracking?token=...&source=video|image&exercise=...

PoseTracker uses a single engine (V3). There is no “V2 vs V3” selection.

How it works (high level)

1. Your app opens the PoseTracker URL in a WebView/iframe

2. PoseTracker runs pose estimation locally in the page

3. PoseTracker emits structured messages to your app (postMessage / WebView bridge)

4. Your app updates UI, stores results, or drives a training flow

Start here:

• Real-time tracking: Use PoseTracker on real-time camera / webcam

• Upload tracking: Use PoseTracker on uploaded files

---

Old solution: Pixel tracking

Pixel tracking is documented in its own section (Deprecated). Those docs are intentionally kept separate and unchanged.Solution 3: Pixel tracking (⚠️ Deprecated ⚠️)

Pixel tracking is deprecated.

Keep it only for legacy integrations.

Docs:

• Pixel tracking (⚠️ Deprecated ⚠️)