Introduction
Let's discover Beoty in less than 5 minutes.
What is
Beoty is Software as a Service (SAAS) provided by PT. Ahli Bangun Sistem (PT. ABS) with the main service is to deliver face recognititation service both for website & mobile apps.
What you'll need
- Subscription
- You need to subscribe a monthly subscription to use Beoty services.
- WebSocket knowledge
- You must familiar with websocket, and related third party service like pusher
Main Flow
The Beoty service are designed to use as as easy as turning over your hand. You just need to implement minimal code base while maintaining your own business logic. Beoty will use WebSocket connection to inform the update of your face recognitation status. Unlike another method, Beoty doesn't use a webhook to provide a callback.
Be prepared:
This is the short flow description
Integrate Beoty SDK to your project
We will inform to you a dedicated SDK only for you
Enrolling Step
- Call the beoty service with main purpose to "enroll / register" the client or user face data
While in this step, is up to you if you want to implement your own business logic,
like save the face data on your own server, or do anything out of beoty service. - Register and listen to websocket event
You must register and listen to websocket event to ensure
you will receive face enrolling response from us - Receiving websocket signal as face enrolling response
Beoty will send the face enrolling status back to you after processing - Done, your face enrolling data has been registered on our end
Verification Step
- Call the beoty service with main purpose to "verify / check" the client or user face data
It's a simple call with simple paramter to request a face verify function - Register and listen to websocket event
You must register and listen to websocket event to ensure
you will receive face verify response from us - Receiving websocket signal as face verify response
Beoty will send the face verify status back to you after processing.
In this step, ideally you will implement your own logical business. You must handle
what will happen if a user are "not verified" and if "verified" by your own end - Done, your face verify request has been complete.