Request a liveness verification link
Issue hosted liveness-check link(s) for a user. Liveness cannot be performed through an API upload — it needs an interactive session — so relay each returned link to the right end user. Returns one link for an individual user and one link per beneficial owner for a business; each entry is tagged with subject (and, for a beneficial owner, person_reference_id and name) so you can route it. The request body is optional; supply redirect to send the user back to your own page after the session (see below). Calling this again for a subject whose link is still active returns that same link rather than issuing a new one — unless you supply a different redirect, which mints a fresh link. Completion is reported per link via the user.liveness_completed webhook and, on approval, a verification report is attached to the user. A liveness result never changes the user’s status. The redirect landing is a UX convenience, not the result — always treat the user.liveness_completed webhook as the source of truth, since a session can still be held or expire after the user sees a success page.
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.
"2026-04-14"
Path Parameters
User UUID.
Body
Optional. Where to send the user after the hosted session, instead of the default completion screen. Opt-in per client: each URL must be HTTPS and its host must be on your redirect allowlist; an unlisted or non-HTTPS URL is rejected with 422. The allowlist is configured by the Kira team — there is no API or dashboard for it: email support@kirafin.ai with the domains you want allowlisted (subdomain matches are allowed) and the environments they apply to. Until they are registered, any request carrying a redirect returns 422. Omit to keep the default completion screen. Bound to the link when it is issued — a repeat call with a different redirect mints a new link.
Response
Liveness link(s) issued — one entry per subject.
One entry for an individual user, one per beneficial owner for a business.