KOkobaltlabs
marketing-requirement-tuning

List Requirement Tests

This rule's recent tests, newest first — the attempts the loop is made of.

Reaps first, so a test abandoned by a restarted process reads as stopped rather than running. A read that writes, deliberately: the alternative is a row nobody can ever leave, which is worse than a GET with a side effect nobody can observe except as the truth.

get/marketing/requirement-tuning/requirements/{requirement_id}/tests

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/marketing/requirement-tuning/requirements/{requirement_id}/tests
  • Auth
    none declared

Path parameters

requirement_idstring uuid required

Query parameters

limitinteger

Response

Successful Response

test_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.

createdstring date-time required
finished_atstring date-time nullable
requirement_textstring required
tests_current_revisionboolean

Changes

No recorded changes to this operation across all 8 revisions of this API.