curl -X POST "https://api.fitsociety.io/public/v1/workout/performance/sessions/start" \
-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({programmeScheduleItemId: '67f1234567890abcdef1234', plannedDate: '2026-09-09'})
};
fetch('https://api.fitsociety.io/public/v1/workout/performance/sessions/start', 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/sessions/start"
payload = {
"programmeScheduleItemId": "67f1234567890abcdef1234",
"plannedDate": "2026-09-09"
}
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Start, continue, fully reset, or clear freestyle performance
For an ordinary recurring plan day, a normal start after completion creates a new session with fresh performances and preserves all prior sessions and results. No refresh, resumeAction, or confirmation token is needed when no active attempt exists. Active/paused attempts retain the existing confirmation flow. A matching active session can still be continued after its plan or day is removed; removed prescriptions cannot start a new session. Explicit plan restarts preserve prior completed performances. A confirmation token is valid for ten minutes and can be consumed once for its active attempt. A stale continue/restart confirmation never creates a new attempt; if the attempt changed, reload its current state and obtain a fresh confirmation before retrying.
Requires the workout_sessions:write scope and the corresponding Workout features and permissions.
curl -X POST "https://api.fitsociety.io/public/v1/workout/performance/sessions/start" \
-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({programmeScheduleItemId: '67f1234567890abcdef1234', plannedDate: '2026-09-09'})
};
fetch('https://api.fitsociety.io/public/v1/workout/performance/sessions/start', 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/sessions/start"
payload = {
"programmeScheduleItemId": "67f1234567890abcdef1234",
"plannedDate": "2026-09-09"
}
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Authorizations
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"
Body
- Option 1
- Option 2