curl -X PATCH "https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/days/{weekday}/items/reorder" \
-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({
itemIds: [
'6aba07aede84bbc66debe0cf',
'6aba07aede84bbc66debe0ca',
'6aba07aede84bbc66debe0cb'
]
})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/days/{weekday}/items/reorder', 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}/days/{weekday}/items/reorder"
payload = { "itemIds": ["6aba07aede84bbc66debe0cf", "6aba07aede84bbc66debe0ca", "6aba07aede84bbc66debe0cb"] }
headers = {
"Idempotency-Key": "<idempotency-key>",
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)Reorder the items inside one day of the client's own programme
Reorder the ITEMS inside ONE DAY of the client’s own programme — the workouts and activities returned as week.days[].items[] by the template-with-progress endpoint. Nothing moves between days: only order within that single weekday is renumbered.
itemIds must be an exact permutation of that day’s item _ids, in the new top-to-bottom order; order is reassigned 1..n to match, which is the field the week view sorts each day’s items by. Item identity and every type-specific field travel with the item untouched — planMomentId for a workout, and activityType / name / description / startTime / plannedDurationMinutes / targetDistanceMeters for an activity.
A PARTIAL list is refused: leaving items unnamed would give them no defined position, and an id belonging to another day would silently move it across days. Both return WORKOUTPLAN_ITEM_ORDER_INVALID.
The weekday must be an AUTHORED day of that week — days[] is stored sparsely, so a weekday the week view merely pads in has no items to reorder and returns WORKOUTPLAN_WEEKDAY_NOT_FOUND.
The client counterpart of PATCH /app/v1/workout/plans/template/{planId}/weeks/{weekNumber}/days/{weekday}/items/reorder — same body, same rules, same response shape. It differs only in who it lets in: the plan is pinned to the caller’s own ASSIGNED calendar programme, so a client can never reorder a library template or another client’s plan.
Requires the workout_client_plans:write scope. This operation maps to /app/v1/workout/plans/client/template/:templateId/weeks/:weekNumber/days/:weekday/items/reorder 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}/days/{weekday}/items/reorder" \
-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({
itemIds: [
'6aba07aede84bbc66debe0cf',
'6aba07aede84bbc66debe0ca',
'6aba07aede84bbc66debe0cb'
]
})
};
fetch('https://api.fitsociety.io/public/v1/workout/clients/{clientId}/plans/template/{templateId}/weeks/{weekNumber}/days/{weekday}/items/reorder', 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}/days/{weekday}/items/reorder"
payload = { "itemIds": ["6aba07aede84bbc66debe0cf", "6aba07aede84bbc66debe0ca", "6aba07aede84bbc66debe0cb"] }
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
The client's own assigned calendar plan.
"67f1234567890abcdef1234"
The 1-based week of the schedule.
x >= 11
The weekday whose items are being reordered. 1 = Monday … 7 = Sunday.
1 <= x <= 71
Client in the company bound to the Public API token.
^[a-fA-F0-9]{24}$Body
Every item _id of that day, exactly once, in the new top-to-bottom order.
1[ "6aba07aede84bbc66debe0cf", "6aba07aede84bbc66debe0ca", "6aba07aede84bbc66debe0cb" ]