در حال بارگذاری…
Publish one logged workout set as a strength-record claim.
| Permission | Description |
|---|---|
strength_records.view | Access the strength-record group |
strength_records.create | Publish a claim |
| Name | Type | Required | Description |
|---|---|---|---|
tracker_workout_set_id | integer | Yes |
| A set you logged, carrying a catalog exercise and a rep count (a custom, free-text set is a 422) |
user_id, exercise_id, rep_count and weight are never read from the request. The last three
are copied from the set server-side, once, and are not updated afterwards: see
Strength Record Claim Resource.
Nothing an athlete logs is public until this endpoint is called. A user who has never claimed a set does not appear on any leaderboard.
{
"data": { /* strength record claim resource */ }
}
Returned when the set already had a claim that you had withdrawn. The same claim is
republished: withdrawn_at goes back to null and the existing verification count is kept, so
withdrawing and re-claiming is not a way to reset a count.
| Status | Error Type | Reference |
|---|---|---|
| 422 | Validation Error. Also returned when the set carries no exercise or no rep count and therefore cannot be ranked. | Validation error |
| 401 | Unauthorized | Authentication error |
| 403 | Forbidden | Permission error |
| 404 | The set is not yours. A set belonging to someone else and a set that does not exist return the same 404, so the endpoint cannot be used to discover which set IDs exist. | Not found error |