Create an Inquiry via POST /api/v1/inquiries using the Persona API key; specify the template ID corresponding to the desired verification configuration (e.g., government ID + selfie).
Embed the Inquiry flow in your frontend using the Persona.js SDK or redirect the user to the hosted flow URL returned in the inquiry response.
Handle the completed, failed, and needs_review webhook events at your configured endpoint; Persona signs payloads with an HMAC-SHA256 signature using your webhook secret.
After the inquiry completes, retrieve the verification objects via GET /api/v1/inquiries/{inquiry-id} to access extracted document data, field-level match results, and decision output.
Use Persona Workflows to automate downstream actions on inquiry completion: trigger database report lookups, create Cases for manual review queues, or call your own internal APIs.
Test the integration in the Persona sandbox environment using provided synthetic identity and test document profiles before enabling live verifications.
Known gotchas
Template IDs are environment-scoped; a template ID from the sandbox will not work in production and vice versa — maintain separate environment configurations.
Persona's API versioning uses a Persona-Version header; omitting it or using an outdated version may return deprecated field structures for document extraction results.
The Inquiry status needs_review indicates a human review is pending in Persona's system; your integration must handle this asynchronous outcome and not treat it as a synchronous pass/fail.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp