Organization API key. Keys are prefixed with vk_live_ (production) or
vk_sandbox_ (sandbox).
API version date string (e.g. 2026-02-01). If omitted, the version
pinned to your API key is used.
Response key casing. Defaults to snake.
Declares what the workflow is used for. Downstream checks like consortium matching use this to score cross-org matches contextually. For example, the same face at two schools is normal for enrollment but suspicious for financial aid.
Compliance standard to enforce on this workflow. When set to “ial2”, the workflow must include document_ocr, face_match, proof of address, OTP verification, and user info with name fields per NIST SP 800-63-3.
Workflow format — “steps” for legacy array format, “graph” for DAG format.
DAG graph representation of the workflow. Present when format is “graph”. Contains “nodes” (dict of node objects) and “entry” (start node ID).
What the workflow is used for. Used by consortium matching to apply purpose-aware scoring — e.g., financial aid matches are scored higher than enrollment matches.
Compliance standard enforced on this workflow. “ial2” enforces NIST SP 800-63-3 identity proofing requirements.