Verification Check Types

Check types define the automated verification rules that run when a seller submits a delivery. Multiple checks can be combined in a single contract.

New: Extensible Check Library - FinalTX now supports 30+ built-in check types across 17 domains with the ability to create custom checks. See the Checks API for the full library including HTTP, artifact, code repo, supply chain, and AI-assisted checks.

Verifies that an endpoint returns the expected HTTP status code. Useful for confirming an API is deployed and responding.

Fields

urlrequiredstring

URL to check (supports JSONPath from delivery payload)

expected_statusrequirednumber

Expected HTTP status code (e.g., 200, 201, 204)

Example

{
  "type": "http_status",
  "url": "$.artifact_url",
  "expected_status": 200
}

JSONPath Reference

Many check types support JSONPath expressions to extract values from the delivery payload.

$.fieldRoot-level field

$.nested.fieldNested field

$.array[0]First array element

$.array[*].nameAll "name" fields in array

Combining Multiple Checks

Add multiple checks to the verification_checks array. By default, all checks must pass.

{
  "verification_mode": "deterministic",
  "verification_checks": [
    {
      "type": "http_status",
      "url": "$.api_url",
      "expected_status": 200
    },
    {
      "type": "json_match",
      "url": "$.api_url",
      "json_path": "$.version",
      "operator": "gte",
      "expected": "2.0.0"
    }
  ]
}