Sign in
marketing-requirement-tuning

Get Requirement Test

One test, with every item. What the surface polls while a fan-out drains.

Reaps first, like the history list and for a sharper reason: this is the route the panel polls. A test abandoned mid-fan-out by a redeployed web process has no other way to leave running, so without this the panel polls a row that will never change — past every budget, indefinitely — while the reaper waits for somebody to open the history list.

get/marketing/requirement-tuning/tests/{test_id}

Path parameters

test_idstring uuid required

Response

Successful Response

test_idstring uuid required
requirement_idstring uuid required
base_revision_idstring uuid required
status'running' | 'succeeded' | 'partial' | 'failed' required

Where a test is, and how it ended.

RUNNING is the state the request returns in: the row is written and the fan-out dispatched, so the surface has something to poll from the first tick rather than a spinner with nothing behind it.

PARTIAL is its own member rather than a flag on SUCCEEDED. A test where two of twenty-two assets never answered is a real result worth keeping — eighteen answers is the answer — but a suggestion built from it has to know it is reading an incomplete picture, and a reviewer deciding whether their edit worked must not be shown eighteen verdicts as if they were twenty-two.

requirement_textstring required
judging_guidancestring nullable
trigger_termsstring[]
collateral_typesstring[] nullable
marketing_team_idsstring[] nullable
createdstring date-time required
started_atstring date-time nullable
finished_atstring date-time nullable
errorstring nullable
created_by_emailstring nullable
modelstring required
llm_callsinteger

Changes

No recorded changes to this endpoint across all 1 revision of this API.