curl -X PUT "https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'PUT',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({status: 'completed'})
};
fetch('https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}"
payload = { "status": "completed" }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.put(url, json=payload, headers=headers)
print(response.text)Save one programme activity occurrence
Starts, completes, or cancels one non-workout activity from an assigned calendar programme. The path identifies the authored occurrence; retries update that same occurrence. The caller cannot override ownership. Work-block fields require a structured running session and the composite cardio feature flag; legacy totals remain writable while that flag is off. First running logging stores an immutable execution snapshot. Client-supplied completedOnTarget, workBlockEvaluation, resolvedTargetsSnapshot and externalWorkoutRef are rejected. Only the athlete can report a niggle, which sets the profile safety flag before the log save and triggers future intensity suppression afterwards. With the cardio flag enabled, generated-plan execution commits with a transactional plan fence. Pace-led in_progress logs are refused with CARDIO_NIGGLE_ACTIVE while the athlete flag is active; historical completed actuals remain loggable. No pace tolerance or condition correction is invented. An item is executable throughout its available programme week.
Requires the workout_sessions:write scope. This operation maps to /app/v1/workout/performance/activities/:planId/:scheduleItemId/:plannedDate and retains its Workout V2 permission, feature-flag, and resource-scope checks.
The clientId path parameter is resolved inside the company bound to the Public API token when present.
curl -X PUT "https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'PUT',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({status: 'completed'})
};
fetch('https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.fitsociety.io/public/v1/workout/performance/activities/{planId}/{scheduleItemId}/{plannedDate}"
payload = { "status": "completed" }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.put(url, json=payload, headers=headers)
print(response.text)Authorizations
Public API access token issued by /public/v1/oauth/token. Example: Authorization: Bearer fspt_.... Each resource request rechecks the token company's current provider access. Disabling access blocks existing tokens with 403 auth.provider_unavailable.
Headers
Required for Public API write requests. Reusing the same key with the same method, path, and body replays the stored successful response; reusing it with a different request returns 409 idempotency.conflict.
1 - 200"booking-create-20260714-001"
Path Parameters
Assigned workout plan id.
"67f1234567890abcdef1234"
Activity schedule item id.
"67f1234567890abcdef1234"
Canonical planned occurrence date.
^\d{4}-\d{2}-\d{2}$"2026-09-08"
Body
in_progress, completed, cancelled "completed"
Work steps only, identified by persisted block/step ids and a one-based repetition index. Recovery and whole-activity averages cannot supply work evidence. Omission preserves existing entries; an explicit array replaces them.
1000Show child attributes
Show child attributes
Whole-activity mean HR, informational only; never compared with a work-step band.
sick, away, injured, interrupted, too_hard, other Show child attributes
Show child attributes
Authenticated athlete only. Sets the profile niggle active before saving the log. Clearing requires the dedicated athlete endpoint; coaches cannot clear it.
Show child attributes
Show child attributes
Public writes are manual. Consented wearable import is a later phase.
manual Actual activity duration in minutes.
x >= 045
Actual activity distance in meters.
x >= 08000
"Felt smooth."
Perceived exertion from 1 through 10.
1 <= x <= 107