Skip to content

Add a period video to a bout

POST
/api/bouts/{id}/periods/
curl --request POST \
--url http://localhost:8000/api/bouts/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/periods/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "video_url": "https://media.example.com/teams/9b1c7e2a/sessions/2026/10/0c5b1d7e-6a2f-4e3b-8d19-5f0a7c2e4b61.mp4", "lamps": [ [ 0.44, 0.49, 0.47, 0.52 ], [ 0.51, 0.49, 0.54, 0.52 ] ], "strip": [ [ [ 0.33, 0.66 ], [ 0.35, 0.58 ] ], [ [ 0.5, 0.66 ], [ 0.5, 0.58 ] ], [ [ 0.67, 0.66 ], [ 0.65, 0.58 ] ] ] }'

Attaches one uploaded video — one period of the bout — with the scoring-lamp boxes and the three strip lines the coach marked on one frame. With lamps, a background read proposes the touches (detect_status goes pending → running → done / failed); without them detect_status is skipped and the coach marks the touches with PUT /touches/. Costs nothing. Refused (400) past a bout’s period limit, for a video stated longer than a period is read, and while the team already has the most period reads queued; 402 for a read-only team.

id
required
string format: uuid
object
video_url
required

public_url from POST /api/sessions/upload-intent/ — one period of the bout.

string
>= 1 characters <= 1000 characters
duration_s
number format: double
nullable
marked_s

Seconds into the video of the frame the lamps and the strip were marked on. The camera pans and zooms; the marks are carried from this frame. Omitted = the first frame. Within the first 60 s.

number format: double
nullable
lamps

Scoring-lamp boxes [x0, y0, x1, y1], normalised to the frame. Omit when the lamps are out of frame: the coach then marks the touches.

Array<Array<number>>
<= 4 items
strip

Three lines across the strip — both en-garde lines and the centre line — each as two frame points, edge to edge. Their order does not matter.

Array<Array<Array<number>>>
>= 3 items <= 3 items

Examples

ExampleAPeriodWithLampsAndTheStrip

A period with lamps and the strip

{
"video_url": "https://media.example.com/teams/9b1c7e2a/sessions/2026/10/0c5b1d7e-6a2f-4e3b-8d19-5f0a7c2e4b61.mp4",
"lamps": [
[
0.44,
0.49,
0.47,
0.52
],
[
0.51,
0.49,
0.54,
0.52
]
],
"strip": [
[
[
0.33,
0.66
],
[
0.35,
0.58
]
],
[
[
0.5,
0.66
],
[
0.5,
0.58
]
],
[
[
0.67,
0.66
],
[
0.65,
0.58
]
]
]
}
Media typeapplication/json
object
id
required
string format: uuid
index
required
integer
video_url
required
string format: uri
duration_s
required
number format: double
nullable
calibration
required
detect_status
required
string
Allowed values: pending running done failed skipped
detect_error
required
string

Examples

ExampleThePeriod,ItsLampsQueuedForReading

The period, its lamps queued for reading

{
"id": "a3e1c9f0-52b7-4d16-8c0e-91f4b2d7e6a5",
"index": 0,
"video_url": "https://media.example.com/teams/9b1c7e2a/sessions/2026/10/0c5b1d7e-6a2f-4e3b-8d19-5f0a7c2e4b61.mp4",
"duration_s": null,
"calibration": {
"lamps": [
[
0.44,
0.49,
0.47,
0.52
],
[
0.51,
0.49,
0.54,
0.52
]
]
},
"detect_status": "pending",
"detect_error": ""
}
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string

Example generated

{
"detail": "example"
}
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string

Example generated

{
"detail": "example"
}
Media typeapplication/json
object
detail
required

One of eight canonical strings. The front-end paywall switches copy + CTA on this value (exact string equality — do not localise). quota_exhausted / seat_limit_reached / client_limit_reached / feature_not_in_plan lead to an upgrade CTA; subscription_suspended leads to a Billing Portal CTA so the buyer can update their payment method; exercise_not_in_plan leads to a contact-us CTA — the movement list is sales-managed, no tier adds to it (#2030). trial_expired / access_ended mean the team is read-only (#2901): everything opens, nothing new is created; they lead to a subscribe CTA and always carry reset_at: null.

  • quota_exhausted - Session quota for the period reached 0
  • subscription_suspended - Stripe dunning in flight (past_due / unpaid)
  • seat_limit_reached - Adding another team member would exceed plan.max_seats
  • client_limit_reached - Adding another Client would exceed plan.max_client_profiles
  • feature_not_in_plan - The tier does not include this whole feature surface
  • exercise_not_in_plan - The (activity, exercise) is not in the team’s exercise grants
  • trial_expired - The team is read-only: its self-serve trial ended
  • access_ended - The team is read-only: its paid plan or granted access ended
string
Allowed values: quota_exhausted subscription_suspended seat_limit_reached client_limit_reached feature_not_in_plan exercise_not_in_plan trial_expired access_ended
reset_at
required

ISO-8601 UTC timestamp the team’s current period ends. Null when the team has no live subscription (legacy un-migrated row). On Free + paid this is the renewal moment; quota refreshes to exactly plan.session_quota (NOT additive — leftover sessions don’t roll over).

string format: date-time
nullable
current_plan
required

The active plan’s role string (free, starter, professional, organization, strategic). Same value as current_role — kept as two separate fields for forward-compatibility with a future named-plan split where current_plan could carry an SKU and current_role the tier label.

string
current_role
required

The active plan’s role string. See current_plan.

string
feature

Which feature surface is locked. Present ONLY on feature_not_in_plan, so one modal can name what’s gated without a detail string per feature (#773). The only value today is agents (aikynetix/agents/services.py::AGENTS_FEATURE).

string

Example

{
"detail": "quota_exhausted"
}
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string

Example generated

{
"detail": "example"
}
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string

Example generated

{
"detail": "example"
}