Skip to main content
POST
Set the engineer's human_decision on a regression check

Authorizations

Authorization
string
header
required

Enter your API key (e.g. dai_sk_test_key_001)

Headers

Authorization
string

Path Parameters

regression_check_id
string
required

Cookies

decimal_session
string | null

Body

application/json

H1095 (improve#673): typed body for the decision endpoint.

Pre-fix the handler took Dict[str, Any] and read only the decision key, so {"action": "approve"} (the persona's typo of the field name) was silently treated as {"decision": None} — clearing any prior decision rather than recording one. The HIGH-severity flag on this item is because the broken-decision-flow runs underneath the regression-check UI's "Approve" button.

Fix: typed body with extra='forbid' so unknown keys 422 + Literal enum on decision so unknown values also 422 (replaces the inline if decision not in ... check below).

decision
enum<string> | null

Engineer's human annotation. null clears any prior decision; intentional/acknowledged/needs_review record one.

Available options:
intentional,
acknowledged,
needs_review

Response

Successful Response