curl -X PATCH "https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/skip" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'PATCH',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({isSkipWeek: true})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/skip', 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/template/{templateId}/weeks/{weekNumber}/skip"
payload = { "isSkipWeek": True }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)Skip a whole week of the client's plan (or resume it)
Marks a whole WEEK of the client’s own programme as SKIPPED, or clears the flag again — the “Skip Week” / “Resume Week” option on the week sheet.
A skipped week keeps every day and item it holds; the week just renders as skipped and the plan resumes the next week. So this never touches the week’s days[]. It is independent of the per-day skip and of a day’s rest flag. isSkipWeek: false is the Resume action; idempotent — changed is false when the week already had the flag.
Unlike the day endpoints, the week must already exist — a week is never created on demand here.
The flag is surfaced on every screen that lists a plan’s weeks: isSkipWeek on getWorkoutTemplateWithProgress’s week and planWeeks[], on the week detail (…/library/template/{templateId}/week/{weekNumber}), and on the weeks overview (…/plans/client/template/{templateId}/weeks).
Requires the workout_client_plans:write scope. This operation maps to /app/v1/workout/plans/client/template/:templateId/weeks/:weekNumber/skip 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 PATCH "https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/skip" \
-H "Authorization: Bearer <access_token>" \
-H "Idempotency-Key: <stable_request_key>" \
-H "Content-Type: application/json" \
-d '{}'const options = {
method: 'PATCH',
headers: {
'Idempotency-Key': '<idempotency-key>',
Authorization: 'Bearer <token>',
'Content-Type': 'application/json'
},
body: JSON.stringify({isSkipWeek: true})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/skip', 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/template/{templateId}/weeks/{weekNumber}/skip"
payload = { "isSkipWeek": True }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(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"
The 1-based week of the calendar schedule.
x >= 11
Client in the company bound to the Public API token.
^[a-fA-F0-9]{24}$