Skip to main content
Subjects let you group analyses by individual runner. Create a subject record, then pass the 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
If you only run one-off analyses without tracking individual runners, you can skip subject management entirely.

Create a subject

All body fields are optional. The server generates a unique subject_id. Height must be in meters and weight in kilograms (metric system).
Response (201 Created):
Pass subject_id as a form field when starting an analysis:
The analysis is stored with a reference to the subject. You can then retrieve all analyses for that subject using the subject analyses endpoint. When you list all analyses, each item includes the subject_id field if a subject was linked.

List all subjects

Response:

Get a single subject

Returns the subject object, or 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.
Response:

Delete a subject

Subjects are soft-deleted — the record is kept but excluded from list results. The endpoint uses POST instead of DELETE to prevent accidental deletion.
Response:

List analyses for a subject

Retrieve all analysis IDs linked to a specific subject:
Response:

Subject fields reference