Skip to content
AiKYNETIX

Revert a phase still to the analyzer's frame

DELETE
/api/solutions/runs/{run_id}/phase-frame/
curl --request DELETE \
  --url 'http://localhost:8000/api/solutions/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/phase-frame/?block_id=phase-breakdown-1&phase_id=example' \
  --header 'Authorization: Bearer <token>'

Drops the coach’s phase-frame override (and garbage-collects the stored frame); the phase falls back to the analyzer-picked still everywhere the report renders. Idempotent — reverting a phase that has no override returns reverted: false.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
run_id
required
string format: uuid

Query Parameters

Section titled “Query Parameters”
attempt_id
string

Per-trial payload id for multi-attempt reports; omit for single-attempt reports.

block_id
required
string
Allowed values: phase-breakdown-1 phase-slider-1

phase-slider-1 / phase-breakdown-1.

phase_id
required
string

Analyzer phase name (the phase’s id in the block).

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json

200 from the phase-frame revert.

object
reverted
required

true when an override existed and was removed; false when the phase was already on the analyzer’s frame (idempotent).

boolean
Examples
ExampleOverrideRemoved

Override removed

{
  "reverted": true
}

400

Section titled “400”
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
Examplegenerated
{
  "detail": "example"
}

401

Section titled “401”
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
Examplegenerated
{
  "detail": "example"
}

404

Section titled “404”
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
Examplegenerated
{
  "detail": "example"
}