MATCH or MISMATCH decision, and verification metadata within under 3 seconds.
Use it during KYC onboarding, account recovery, fraud prevention, and any workflow where you need to confirm a user’s identity against a known reference.
Overview
Sandbox testing is not available for the Face Match API. Use your live credentials and real images during development.
Endpoint
Headers
Request body
string
required
The trusted reference image to compare against. Typically a government-issued ID photo retrieved from a LumiID verification API. Accepts a Base64-encoded string or a publicly accessible image URL.
string
required
The live selfie captured from your user during the current session. Accepts a Base64-encoded string or a publicly accessible image URL.
string
required
A unique, client-generated key that identifies this specific comparison request. Reuse the same key when retrying a failed request to prevent duplicate processing and billing.
Example request
Success response
Response fields
boolean
Indicates whether the comparison completed successfully.
string
Machine-readable result code (e.g.
FACE_MATCH_CONFIRMED).string
Human-readable result message.
object
High-level verification summary.
object
Face comparison result.
object
Request metadata.
Decision guide
Use
decision as the authoritative outcome. similarity_score provides additional context, and margin_band signals how close the result was to the decision boundary — but neither should override decision in automated workflows.Error codes
Best practices
- Always run Liveness Detection before Face Match to confirm the selfie came from a real, live person.
- Ensure only one face appears in each image before submitting.
- Use well-lit, front-facing images for both the reference and probe.
- Submit original camera images — avoid screenshots or images forwarded through messaging apps.
- Use government-issued photos retrieved directly from LumiID verification APIs as your
reference_imagefor maximum accuracy and compliance.
Code example
Python