Garmin-first training planning, with athlete approval.

Use a bounded connector while official access is pending

Pitwall is preparing an integration through the Garmin Connect Developer Program. The requested first release covers completed activities through the Activity API and athlete-approved workout publication through the Training API.

For the controlled beta, an explicitly experimental connector can establish a Garmin session from credentials supplied by the athlete. Passwords and MFA codes are used only for that authentication step and are not stored. The connector uses services outside Garmin's public developer API, can stop working, and is not presented as official Garmin support.

Let the watch record the work

Garmin devices and Garmin Connect already record and synchronize training. Pitwall is not rebuilding that system. Its role is to place an imported completed activity beside the target that existed before the session and make the difference easier to review.

• Receive approved activity data after athlete consent.
• Normalize provider details into a provider-neutral activity record.
• Deduplicate retries before they become multiple completed sessions.

Approve before a workout goes back

If Training API access and compatible workout mapping are approved, Pitwall is intended to let an athlete review a structured workout before publishing it to the Garmin Connect calendar. The athlete should see what changed and why before anything is sent.

Garmin is the first connector because the initial athletes use Garmin devices. It is not the identity of Pitwall, and the core planning model is designed to support other providers later without rebuilding athlete history.