Standard Amiqus Integration Flow

This guide walks you through creating a new Amiqus check during a user’s registration on your website. The steps focus on the key Amiqus API endpoints and the recommended webhook setup.

Prerequisites

• Webhook registration: Ensure you have configured a webhook endpoint to receive record update notifications. You can use the webhook setup guide to get started. This will allow you to track when a user has completed their Amiqus check.
• Amiqus API credentials: You will need valid credentials to call the Create a Client and Create a Record endpoints.

Overview of the flow

Below is a diagram illustrating the overall process. Once the user registers on your website and provides their details, you will create a client and then create a record in Amiqus. Amiqus will email the user to complete their checks, and your webhook will notify you when the checks are done.

Step-by-step guide

1. User registration on your website

During your user’s normal sign-up process, ensure you collect at least:

• Full name
• Email address

These fields are required when creating a client in Amiqus.

2. Initiate the Amiqus check workflow

2.1 Create a Client
Using the Amiqus API, create a client. For example:

{
  "name": {
    "title": "mr",
    "first_name": "Martin",
    "middle_name": "Seamus",
    "last_name": "McFly"
  },
  "email": "marty@example.com"
}

Upon success, you will receive a client_id in the response. Store this client_id to reference later.

2.2 Create a Record
Next, create a new Amiqus record which points to the client you have just created. A record can include a number of checks (referred to as steps in our documentation), such as identity report, banking information, criminal record checks, etc.:

{
  "client": 7832,
  "steps": [
    {
      "type": "check.photo_id",
      "preferences": {
        "report_type": "standard",
        "docs": [
          "passport",
          "driving_licence"
        ]
      }
    }
  ],
  "notification": "email"
}

You’ll receive a record_id in the response. This record triggers the Amiqus check process and sends the invitation email to the user.

Note - If you wish to notify the user outside of Amiqus, you can set the notification value to be false. This will prevent Amiqus from sending the user an email asking them to do the check. The record response has a perform_url value which you can forward to the user however you want to e.g. email, in app, browser etc.

3. Wait for user to complete their checks

Amiqus will send your user an email (where notifications are enabled) containing a link to complete their checks. Once they have submitted the required details:

• Amiqus will update the record’s status.
• A webhook notification will be sent to the endpoint you configured, allowing you to update your system accordingly (e.g. marking a user as verified).

What happens next?

After receiving the record update webhook, you may want to:

1. Confirm the checks passed (or handle any failures/requests for more info). You could do this by retrieving the most up-to-date record to get the overall status of all the checks, or by listing all steps within a record, which will give you the status for each individual check.
2. Update your internal user profile status (e.g. “Verified”).
3. Inform your user of their successful verification.