curl -X POST "https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/history/plan/{planId}" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'POST',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({clientId: '67f1234567890abcdef9999'})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/history/plan/{planId}', 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/clients/{clientId}/plans/history/plan/{planId}"
payload = { "clientId": "67f1234567890abcdef9999" }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Single completed plan — training-plan History detail
Recorded history remains available after its plan or day is removed. Original session labels and performance targets/types are used when captured. Detail for ONE completed training plan — the SAME object shape as a single element of plans[] in the plan History feed tab (POST /app/v1/workout/plans/client/history). Returns { plan } with the plan’s days, each carrying its grouped exercises[] (standalone + superset blocks), plan targets, the ‘Previous’ column, and per-set + exercise-level PR flags. A coach passes clientId in the body; a client resolves from token.
Requires the workout_progress:read scope. This operation maps to /app/v1/workout/plans/client/history/plan/:planId and retains its Workout V2 permission, feature-flag, and resource-scope checks.
The clientId path parameter identifies the client represented by the request context.
curl -X POST "https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/history/plan/{planId}" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'POST',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({clientId: '67f1234567890abcdef9999'})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/history/plan/{planId}', 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/clients/{clientId}/plans/history/plan/{planId}"
payload = { "clientId": "67f1234567890abcdef9999" }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(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 WorkoutPlan id.
"67f1234567890abcdef1234"
Client in the company bound to the Public API token.
^[a-fA-F0-9]{24}$Body
Required when the caller is a coach; inferred from token when the caller is a client.
"67f1234567890abcdef1234"