Products
Face API
Detect, compare and search faces on their own, without a full verification session.
What it does
The face API gives your backend the face operations of the platform as endpoints of their own. You can detect a face in an image, compare two faces, and search for a face. Vector search is available as well.
Operations
| Operation | What it is for |
|---|---|
| Detect | Find the face in an image. |
| Compare | Compare faces with each other. |
| Search | Look for a face among faces you have stored. |
| Vector search | Search by the vector of a face. |
When to use it
- You need face comparison inside your own flow, and no document step.
- You want to build your own search over faces that you store.
- You run verification sessions and also need face operations outside them.
When the document and the selfie belong in one flow, use a KYC session instead. It adds the document checks, liveness and the scenario around them.
How it fits your integration
- Your backend calls the face endpoints with an API token. See authentication.
- The response carries the result of the operation.
- Your system decides what to do with it.
Faces and persons are method groups of REST API 2.0.
Next
Read the REST API overview for the shape of a call, or write to us about your face-only flow.
Questions, answered plainly
What does the face API do?
It offers detect, compare and search for faces as standalone endpoints, plus vector search.
Do I need a verification session to use it?
No. The endpoints work on their own, so a team that needs only biometrics can use them without the document steps.
Where does it sit in REST API 2.0?
Faces and persons are method groups of REST API 2.0, next to KYC, Tokens and Users.
Can I build repeat-user search on it?
Yes, search is one of the standalone operations. Face search as a scenario option is described on the face search page.