Skip to main content

Registry Results Reference

A verified credential carries two layers of result. The standardised verdict — eligibility, statusDetail, status — is what you branch on, and the Workers & Credentials tutorial covers it. Underneath sits registryDetails: what the issuing authority's register actually said, in its own terms. This page is the reference for that block, including the per-credential-type keys inside registryFlags.

Reach for it when you need to show an operator the register's own wording, or when a standardised verdict isn't enough to explain itself — a REVIEW_REQUIRED caused by a condition on a clearance, say, where the condition text only exists in registryFlags.

Where it appears​

Once a credential has been verified, every GET of it returns the latest registry result under attributes.verification.registryDetails — what the issuing authority's register actually said, not just the standardised eligibility/statusDetail verdict. Worker responses with ?include=credentials carry the same object on each credential summary.

"verification": {
  "status": "ACTIVE",
  "eligibility": "MAY_ENGAGE",
  "statusDetail": "VALID",
  "lastVerifiedDate": "2026-08-01",
  "registryDetails": {
    "registryCardType": "Work Entitlement",
    "registryHolderName": "JANE CITIZEN",
    "registryIdentifier": "PA1234567",
    "registryExpiryDate": "2027-03-15",
    "lastVerifiedAt": "2026-08-01T02:11:05Z",
    "verificationMethod": "ONGOING",
    "sourceSystem": "vevo",
    "registryFlags": {
      "visa_class": "TSS/482",
      "visa_subclass": "482",
      "entitlement_status": "Entitled to work"
    }
  }
}

The block is type-agnostic: the structured fields are filled where the registry provides them (some registries publish no expiry or holder name), and registryFlags carries the credential-type-specific detail verbatim — the same keys the credential.verified webhook sends.

registryDetails is absent on credentials that have never been verified against a registry.

registryFlags by credential type​

registryFlags is an open map, so treat any key as optional and never assume the set below is exhaustive — a register can add a field without an API change. These are the keys that recur:

Credential typeTypical registryFlags keys
VEVO (right to work)visa_class, visa_subclass, visa_stream, condition_code, condition_description, country_of_issue, grant_date, grant_expiry, entitlement_status, entitlement_type, status_message, is_conditional
AHPRAis_conditional, ahpra_non_practising, conditions_text, notations_text, undertakings_text, endorsements_text, registration_requirements_text, reprimands_text
WWCC (state checks)card_type, wwcc_sa_status_raw, is_new_card, is_application, suspension, exclusion, expiring
Teacher registration boardsregistration_type / category / member_status / registration_status, registration_since, fee_due_date, expiring
NDIS Worker Screening (NDWS)ndws_pending, ndws_interim_bar, ndws_exclusion, ndws_suspension, ndws_no_valid_clearance, ndws_raw_status
Police checks (NPC/NCC)none — structured fields only