GET

Trust & identity

Get verification

/api/v2/trust/verifications/{verification_uuid}

AUTHENTICATIONBearer token · trust:readService owneridentity-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return verification state and evidence visible to the caller.

When to use it

Poll or reconcile one subject-owned verification after start, using the canonical returned identifier.

OUTCOME · Verify

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to verify verification.
Separates subject identity, consent, evidence, provider output, review, issuer credentials, and relying-party acceptance instead of collapsing them into a universal trust score.

ISOLATION + AUTHORITY

Bearer subject, tenant, purpose, policy version, role, issuer, reviewer, provider, and relying-party boundaries remain distinct. The response or transition grants no payment, custody, settlement, publisher, matching, or trading authority and must not expose regulated evidence beyond the live schema.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required verification_uuid (path) exactly as defined by the live contract.
Resolve the applicable purpose, policy version, consent or role basis, and required assurance before relying on this result.

WHAT TO DO NEXT

Compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
Use the returned lifecycle state and policy version to choose the next least-privilege trust action; do not infer a missing stage.

AGENT GUIDANCE

Use verification only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required verification_uuid (path) exactly as defined by the live contract.
Treat policy availability, consent, evidence capture, completed checks, review, decision, credential issuance, validity, and relying-party acceptance as separate facts.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the trust:read scope.EXAMPLEBearer hc_live_…

verification_uuidpathRequired

32-character lowercase identifierSubject-owned verification identifier returned by the start route.EXAMPLEaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

RESPONSES

Status and payload examples

200Minimized verification, check, and evidence-commitment lifecycle.Read completed · JSON RESPONSE+

{
  "verification_id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "policy": {
    "id": "individual_standard",
    "version": "2026-07-15.1",
    "name": "Individual Standard",
    "description": "Government document, ownership, liveness, and current sanctions screening.",
    "assurance_level": "HC-IAL2",
    "retention_days": 365,
    "checks": [
      {
        "id": "profile",
        "label": "Profile resolution",
        "category": "identity",
        "required": true,
        "freshness_days": 365
      },
      {
        "id": "document",
        "label": "Government document",
        "category": "document",
        "required": true,
        "freshness_days": 365
      },
      {
        "id": "liveness",
        "label": "Liveness and face match",
        "category": "biometric",
        "required": true,
        "freshness_days": 365
      },
      {
        "id": "sanctions",
        "label": "Sanctions screening",
        "category": "screening",
        "required": true,
        "freshness_days": 1
      }
    ]
  },
  "status": "CONSENT_REQUIRED",
  "current_step": "preparation",
  "jurisdiction": "US",
  "provider_mode": "ADAPTER_READY",
  "decision": null,
  "investigation_status": "PENDING",
  "retention_until": "2027-09-01T18:10:00Z",
  "submitted_at": null,
  "completed_at": null,
  "created_at": "2026-09-01T18:10:00Z",
  "updated_at": "2026-09-01T18:10:00Z",
  "checks": [
    {
      "check_id": "check-profile-01",
      "type": "profile",
      "status": "PENDING",
      "outcome": null,
      "summary": null,
      "evidence_sha256": null,
      "performed_at": null,
      "expires_at": null
    }
  ],
  "evidence": [
    {
      "evidence_id": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
      "type": "document_front",
      "check_type": "document",
      "media_type": "image/png",
      "size_bytes": 248310,
      "sha256": "cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
      "status": "CAPTURED",
      "created_at": "2026-09-01T18:10:00Z",
      "updated_at": "2026-09-01T18:10:00Z"
    }
  ]
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the subject, claim or credential version, issuer and reviewer authority, evidence commitment, decision, expiry, and revocation status.

404The verification does not exist for the authenticated subject.Resource not visible · JSON RESPONSE+

{
  "code": "trust_verification_not_found",
  "message": "The verification does not exist for the authenticated subject."
}

INTEGRATION DECISIONtrust_verification_not_found

CALLER ACTION: Verify the canonical identifier and authenticated owner boundary. A 404 may intentionally conceal a resource outside the caller's authority.
RETRY SAFETY: Do not retry the unchanged identifier repeatedly. Refresh the relevant collection or lookup before choosing another identifier.
STATE RECONCILIATION: Refresh the subject, claim or credential version, issuer and reviewer authority, evidence commitment, decision, expiry, and revocation status.
ESCALATE WHEN: Escalate when subject binding, evidence minimization, issuer or reviewer authority, decision lineage, expiry, or revocation cannot be established.

422The verification identifier is not canonical.Request must change · JSON RESPONSE+

{
  "code": "invalid_verification_identifier",
  "message": "The verification identifier is not canonical."
}

INTEGRATION DECISIONinvalid_verification_identifier

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. A corrected read may be sent as a new attempt.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Refresh the subject, claim or credential version, issuer and reviewer authority, evidence commitment, decision, expiry, and revocation status.
ESCALATE WHEN: Escalate when subject binding, evidence minimization, issuer or reviewer authority, decision lineage, expiry, or revocation cannot be established.

401The bearer credential is missing or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for subject-scoped trust claims, evidence, credentials, reviews, decisions, presentations, and revocations.
ESCALATE WHEN: Escalate when subject binding, evidence minimization, issuer or reviewer authority, decision lineage, expiry, or revocation cannot be established.

403The credential lacks exact trust:read authority.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks exact trust:read authority."
}

INTEGRATION DECISIONinsufficient_scope

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for subject-scoped trust claims, evidence, credentials, reviews, decisions, presentations, and revocations.
ESCALATE WHEN: Escalate when subject binding, evidence minimization, issuer or reviewer authority, decision lineage, expiry, or revocation cannot be established.

503The authoritative Identity trust service is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "identity_unavailable",
  "message": "The authoritative Identity trust service is unavailable."
}

INTEGRATION DECISIONidentity_unavailable

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the subject, claim or credential version, issuer and reviewer authority, evidence commitment, decision, expiry, and revocation status.
ESCALATE WHEN: Escalate when subject binding, evidence minimization, issuer or reviewer authority, decision lineage, expiry, or revocation cannot be established.

OPERATIONAL NOTES

Security and lifecycle guarantees

decision, submitted_at, completed_at, retention_until, check outcomes, and check timestamps are nullable until their lifecycle transition occurs. Null is not equivalent to failure or zero.
Refresh this no-store projection instead of predicting state client-side. A completed check is not automatically a final verification decision.
The response excludes identity documents, biometric bytes, screening matches, provider credentials, and reviewer notes. It grants no retrieval, disclosure, transfer, payment, trading, or administrative authority.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory