Skip to main content

Introduction

Facia, a UK-based Software as a Service (SaaS) provider, is at the forefront of Liveness verification services, reaching and serving clients globally. This solution not only aids companies in identifying and mitigating fraud risks but also boasts a user-friendly interface with a seamless API integration process. Businesses can effortlessly onboard legitimate customers and cultivate dependable B2B relationships. Facia's versatile verification services are tailored for diverse industries, including FinTechs, Virtual Asset Service Providers, banks, and more. Choosing Facia translates to combating crimes, boosting productivity, and elevating conversion rates in less than a second.

Services​

Facia is an industry leader in facial biometrics and facial recognition services. Our services include:

  1. 3D Liveness Detection
  2. Detail Liveness Detection
  3. Face Match
  4. Face Search
  5. Age Estimation
  6. Document Verification
  7. Deepfake Liveness Detection
  8. KYC (Interactive)
  9. KYC (Non-Interactive)

This guide helps the developer understand the aforementioned services via the endpoints and outlines the flow of each API.

Registration​

The registration process is a simple three-step process:

  1. You reach out to our representative at support@facia.ai.
  2. You will receive a password-generating link in your provided email.
  3. You should use the email and password or client-id and client-secret to generate an access token using the /request-access-token endpoint.

Integration​

When you have successfully completed the registration process, gaining access to the liveness-based service requires hitting the route /request-access-token. Provide your valid client credentials to obtain a token for authorization in return.

Your credentials are crucial and carry many privileges, you surely don't want to encounter trouble, so be sure to keep your personal and sensitive information guarded! It is highly recommended not to share your credentials in public places such as GitHub or client-side code.

Before we proceed any further, please note that API requests from your side must be made over HTTPS. Calls made over plain HTTP or without authentication will eventually lead to failure.


note

Request bodies should have Content-Type: application/json and be valid JSON. Endpoints that take images also accept multipart/form-data file uploads (see Sending Images). In order to get a JSON response in return, use the HTTP Header Accept: application/json.


info

Facia uses following BASE URL for every request: https://api.facia.ai/

Sending Images​

Image fields (for example file, face_frame, id_frame) can be sent in two ways:

  • application/json: send the image as a Base64 data URI including the prefix, e.g. data:image/jpeg;base64,/9j/4AAQ.... Plain Base64 without the data:image/...;base64, prefix is rejected.
  • multipart/form-data: upload the image file itself (.jpg, .jpeg, .png).

Videos (file_type=video) can only be uploaded as a .mp4 or .mov file with multipart/form-data (max 15 MB). Base64 is not accepted for video.

Using Base64 images in Postman​

Base64 strings are long, so it is easier to keep them in Postman variables than to paste them into every request body.

  1. Convert your image to a Base64 data URI (including the data:image/jpeg;base64, prefix).
  2. Save it in a Postman environment or collection variable, for example front_base64.
  3. Reference the variable in the JSON body. Always wrap the variable name in double quotes, because the value is a JSON string:
{
  "file": "{{front_base64}}"
}
caution

Writing "file": {{front_base64}} without the quotes produces invalid JSON, and the request will be rejected.

Permissions​

The following permissions are required for Facia's API SDKs to function correctly:

  1. Camera Permission
  2. Internet Permission
Note

All the permissions are already handled in SDKs