Send an identity verification
Starts an identity verification and sends the recipient an email with a link to complete it, unless mute is true — then no email is sent and you use accessUrl from the response instead.
Who to verify
entityKey— reference an existing client. You may overrideentityEmailorentityMobilefor this invitation only.- Omit
entityKeyand supplyentityName,entityEmail, and optionallyentityMobilefor someone not yet on file.
AML
- Omit
includeAmlfor identity verification only. - Set
includeAmlto"Basic"or"Extensive"to include AML screening.
For a standalone AML check (no IDV invite), use POST /api/v1/id-verifications/aml-checks.
Cost (wallet in the response)
wallet.identityVerificationFromWallet— amount taken from the practice wallet for the identity check itself (after promotions).wallet.amlOnWalletBecausePoolEmpty— extra wallet charge for AML only when you included AML and the practice had no subscription requests left (then AML is billed like one purchased request). Otherwise 0 (AML used a pool request, no AML on the invite, or AML charges are waived).wallet.totalWalletRequired—identityVerificationFromWallet+amlOnWalletBecausePoolEmpty. If the wallet is short and auto-topup is enabled, the practice wallet is topped up first; otherwise the send fails with 400 when balance is below this total.
Write access is required (canWrite: true from GET /api/v1/auth/validate).
429 — rate limit exceeded.
Authorizations
Swagger / Postman only: Client ID as username, Client secret as password. In Postman, set this once on the collection (Authorization → Basic Auth) so all requests inherit. For production server-to-server code, prefer X-OM-Auth-ID and X-OM-Auth-Key headers.