Skip to main content
GET
Get Validation Results
Retrieve the status and result of a v3 validation job started via Validate Content. Poll this endpoint until status is done or failed.

Path Parameters

string
required
The job_id returned by Validate Content.

Response

string
Always v3.
string
Unique identifier for the validation job.
string
Job status: started, in_progress, done, or failed.
string
Engine that produced the result: v2_frontier or anchor_3_0.
string
Present when an anchor_3_0 request failed and fell back to v2_frontier automatically.
string
Time when the validation job started.
string
Time when this result snapshot was generated.
string
Error details (present only when status is failed).
string
Overall compliance assessment: approved, needs_changes, or do not send. Note: do not send contains spaces — this matches the API response exactly.
object
Violation counts by severity.
integer
Number of lines with at least one compliance violation. Absent for older jobs or when only grouped fixes exist (per-line positions unavailable).
integer
Number of lines with no violations. Absent for older jobs or when only grouped fixes exist.
integer
Total number of lines in the document. Absent for older jobs or when only grouped fixes exist.
True when more than one fix is found, suggesting a re-scan after applying fixes.
array
Rule IDs the model identified as relevant to the content. Present for the anchor_3_0 engine (the SLM’s per-request evaluated rule set); absent for v2_frontier.
integer
Input (prompt) tokens the anchor_3_0 SLM consumed for this validation. Present for the anchor_3_0 engine; absent for v2_frontier (which tracks usage separately).
integer
Output (generated) tokens the anchor_3_0 SLM produced for this validation. Present for the anchor_3_0 engine; absent for v2_frontier.
array
One entry per violating line, with all rules violated and the best fix. Absent for older jobs or when only grouped fixes exist. Present but empty for fully compliant documents.
array
Individual fix entries (rule-centric, one per violation per quote). Each entry carries rule_id — the canonical rule identifier (rule-pack id, or cust_{customer_id}_{id} for activated custom rules).
object
Grouped fixes for rules that aggregate across pages. Each value additionally carries rule_id (the canonical rule identifier — also the key under which the group is stored in this object).
object
Document metadata used for scenario matching.

Status Values

Error Responses

Example