JavaScript

The LEM Verify API and webhook integration is organised around REST using standard HTTP response codes and verbs.
The current version of our API generates unique URLs for verifications, such as Combination, Document and Liveness, along with a notification system in the form of Webhooks.
When a verification has been processed by the system, LEM Verify will send a POST request (Webhooks) to the selected webhook URL with the result, details and PDF report for further processing by your system.

https://api.lemverify.io

Example Use Case - Generate unique URL for Document and Liveness request

Your system needs to verify a person's identity for your KYC/AML process. By making a simple API call to "Request a Combination" (a combination of document and liveness verificaiton) you will obtain a unique URL that your end users navigate to in order to securly submit their documents for processing by the LEM Verify systems.

Once the verification results have been processed, our systems will notify your server via a Webhook with the results of the verification for further processing or data storage by your server.

Example Use Case - Upload an Identity Document for verification (IDV)

You wish to collect the indviduals identity documents from within your own system (or already have them stored). By making an API call to our Upload a Document endpoint you can upload the identty document and receive a document verification report without having to manually enter any of the individuals information.

Once the verification results have been processed, our systems will notify your server via a Webhook with the results of the verification for further processing or data storage by your server.

Considerations

Always use HTTPS.

The web hook post request contains sensitive personal identifiable information, so be very careful where you send this information!

If the account balance is in arrears the webhook will not be sent, so please ensure your account has sufficient credits at all times, as we will not be able to send a POST request after failing due to insufficient credits.

Ensure you send the x-lem-key header, which is case sensitive, with each request. This can be obtained from the Webhooks section of Connections screen in your dashboard.