TEteaflask
authed

Create Verification Request

Creates the request row and starts the suite-authoring workflow. A request binds to exactly the doc's currently-published revision — any other revision is refused with the 409, so a stale caller can never point a suite at content nobody is reading. An organization with no code to verify against gets the ask recorded born failed as unverifiable — same policy as the publish hook, with no workspace burned to discover it mid-flight. A request already in flight on the revision is answered with a 200 instead of a twin (TEA-1067). If the orchestration service can't be reached the row is honestly settled as failed and the caller gets the 503 — never a request that silently goes nowhere.

post/api/v1/doc-revisions/{revision_id}/verification-requests

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/doc-revisions/{revision_id}/verification-requests
  • Auth
    none declared

Path parameters

revision_idstring uuid required

Response

A request already in flight on this revision is returned

idstring uuid required
organization_idstring uuid required
doc_revision_idstring uuid required
status'queued' | 'working' | 'succeeded' | 'failed' | 'unfunded' required

QUEUED and WORKING are workflow-owned; the rest are settled. UNFUNDED is the funding gate's settled state — not FAILED (nothing broke) and not unverifiable (nothing was judged): the organization had no pocket to pay the model, the error column carries the reason sentence, and the resume sweep requeues the row when money lands.

errorstring nullable required
failure_kind'system' | 'doc_contradicted' | 'suite_not_green' | 'unverifiable' required

How machines route a failed request, beside the prose error sentence: system pages a developer, doc_contradicted sends the doc to the drift rewriter, suite_not_green means the authored suite's official run judged against it, unverifiable is the honest no-page no-loop state — a doc with no code to check against or no checkable claims.

requested_by_user_idstring uuid nullable required
created_atstring date-time required
updated_atstring date-time required

Changes

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