GET

Identity · verification

List verification policies

/api/v2/identity/verification/policies

AUTHENTICATIONBearer token · trust:readService owneridentity-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

List the versioned identity-verification policies available to the authenticated subject, including assurance levels, retention periods, required checks, and freshness windows so a person or agent can select a policy before starting verification.

When to use it

Start a subject verification workflow here to select the least intrusive current policy and disclose its required checks, assurance, freshness, and retention before obtaining consent.

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 policies.
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.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
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 policies only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
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_…

RESPONSES

Status and payload examples

200Versioned verification policies with assurance, retention, required checks, and evidence-freshness requirements.Read completed · JSON RESPONSE+

[
  {
    "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
      }
    ]
  }
]

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.

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

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing, expired, 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 explicitly provisioned trust:read authority.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks explicitly provisioned 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 catalog is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "identity_unavailable",
  "message": "The authoritative Identity trust catalog 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

Fetch this catalog before POST /api/v2/trust/verifications. An agent should select the least intrusive policy that satisfies the business requirement, present the checks and retention window to the subject, and submit the exact returned id as policy_id.
assurance_level describes what successful policy completion can establish. A listed policy does not mean the subject started, completed, or passed it.
freshness_days is the maximum acceptable age of previously satisfied evidence for that check. Zero means the owner policy did not publish a reusable freshness window; it does not mean evidence never expires.
The catalog is read-only and accepts no query parameters or request body. It cannot start verification, upload evidence, issue a credential, or grant reviewer authority. Responses are no-store.

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