subject_id when starting an analysis to link them together.
Later, retrieve all analyses for a subject in a single call.
Typical workflow
When to use subjects
Subjects are optional. They are useful when you need to:- Track analyses per runner across multiple sessions
- Store basic runner metadata (name, email, height, weight) once and reuse it
- List all analyses for a specific runner
Create a subject
All body fields are optional. The server generates a uniquesubject_id.
Height must be in meters and weight in kilograms (metric system).
201 Created):
Link an analysis to a subject
Passsubject_id as a form field when starting an analysis:
subject_id field if a subject was linked.
List all subjects
Get a single subject
404 if the subject does not exist or has been deleted.
Update a subject
Only the provided fields are updated. Omitted fields remain unchanged. Same units as creation:height in meters, weight in kilograms.
Delete a subject
Subjects are soft-deleted — the record is kept but excluded from list results. The endpoint usesPOST instead of DELETE to prevent accidental deletion.