Parameters
All reserved parameters (whether input or output) use the re prefix (e.g., reSignature).
Input parameters
If IncludeCustomInputParameters is true in the Verification Result configuration then all non-reserved parameters are bypassed.
Reserved parameters
Session Overrides
Signature (reSignature)
Expiration (reExpiration)
UTC unix epoch (seconds) at which the signed URL expires. After this timestamp the verification will be rejected with 410 Gone.
Set automatically by the create-signature endpoint when SecuritySettings.ExpirationEnabled is true.
Nonce (reNonce)
One-time-use identifier (GUID without dashes). The first successful session consumes the nonce; further attempts to open the same URL are rejected with 410 Gone.
Set automatically by the create-signature endpoint when SecuritySettings.EnableNonce is true. Nonce requires expiration to be enabled.
Language (reLang)
Sets the language of the verification UI for the session. Optional — defaults to en.
https://.../verification/{verificationId}?reLang=deSupported values:
en bg cs da de el es et fi fr hu id it ja ko lt lv nb nl pl pt-BR pt-PT ro ru sk sl sv tr uk zh-Hans zh-Hant
Values are case-insensitive, and _ is accepted in place of -. A tag is resolved by exact match first, then by a known alias, then by its base language — so de-AT resolves to de, zh-TW to zh-Hant, zh-CN to zh-Hans, pt to pt-PT, and no to nb. Portuguese and Chinese ship only as variants, so a bare pt or zh resolves to the alias above.
An unrecognised value falls back to en rather than failing the session.
reLang is part of the signed query string. Add it before generating the signature — appending it to an already-signed URL invalidates reSignature.
External identifier (reExternalId)
Some face recognition modes require a stable external identifier to link a user across sessions.
reExternalIdis required when face recognition is configured for:MatchVerificationUniqueMatchVerificationMatchOnlyVerification
reExternalIdis optional in other modes.
Reserved names with no public meaning
These are reserved and used internally. They are documented here because they behave like any other
reserved name: they are stripped from customInputParameters, so a parameter of your own with one of
these names arrives at the session, returns 200, redirects normally — and is simply absent from the
result, with nothing to debug against.
Use your own prefix
Any parameter beginning with re may become reserved in a future release, whether or not it is listed
today. A name that works now can stop being passed through without anything failing. Use a prefix of
your own for your parameters.
Output parameters
An empty value is not false
A result parameter you enabled can arrive with its value empty — reHappy= rather than reHappy=true.
That means the verifier did not run, or ran and returned no answer for that field. Read an empty value
as "not available"; reading it as false turns the absence of a measurement into one.
Result URL contract (integration output)
The result redirect URL is the primary integration contract.
- VerifEye redirects the browser to your configured result URL.
- The final URL contains query parameters describing the outcome.
- A signature parameter is appended to enable tamper detection.
The following parameter names are used:
reVerificationSessionIdreVerificationResultreLivenessResultreFaceRecognitionResultreAgeVerificationResultreGenderVerificationResultreFaceIdreAgereGenderreConfusionreContemptreDisgustreHappyreEmpathyreSurpriserePresencereEyesOnScreenreAttentionreCorrelationIdreTotalFaceCountreImageIdreFailedReasonreSignature
Parameter presence depends on your project configuration.
Last updated: 2026-09-28