Skip to main content
The flowType in the Create Verification response tells you what happens between create and userinfo. Every create response also carries connectionInstanceId, connectionId, credentialId, providerId, verificationModel, and expiresAt (30 minutes after creation). For the status list, see Verification Flow. For polling, see REST API Integration.
The user signs in on the provider’s page and returns to your redirectUri. Examples: mitid, id-austria, cz-bankid-identify.
Create response
Your app: send the user to flowDetails.authorizationUrl. When the user is back on your redirectUri, check the status.
  • redirectUri: required with REST (400 VALIDATION_REDIRECT_URI_REQUIRED without it). Any valid URL works, but a production app refuses localhost. With OIDC, redirect_uri must be in the app’s Redirect URL Allowlist instead; see Hosted OIDC.
  • What Hopae adds to it: verificationId, appId, and your state. The result parameters (status, result, error, error_description, idp_error, idp_error_description) are still sent but deprecated. Read the result with GET /verifications/{id}: the URL is not proof of the result.

Same-device journeys

A phone cannot scan a QR code it is showing. When the verification starts on a phone, don’t show a QR code. Open authorizationUrl (redirect), qrData as a link (QR; see QR for the connections that differ), or linkData (DC). Keep the verificationId before leaving your app, and resume when the user is back. See Mobile App Integration.