OK
The JSON verdict every /v1/validate/* endpoint answers with on HTTP 200, whether the document passed or failed (the /report siblings answer with a PDF instead).
true when the document passed every fatal rule.
One sentence summarising the verdict.
Outcome per validation layer plus the profile the document was checked against. Which fields are present depends on the endpoint and on how far validation got.
Fatal findings. Empty when Valid is true.
Non-blocking findings (Schematron warnings and advisories such as an unrecognised profile). Never affect the verdict.
The invoice's Business Terms (BT-x) with their values and the findings attached to each, for field-level display. null when the document could not be parsed into the invoice model. Absent on /v1/validate/order-x and when no invoice XML could be read (a PDF without an embedded XML, or one embedding the wrong syntax).
No recorded changes to this operation across all 1 revision of this API.