Introduction

MeetingLawyers can integrate with your company's API to determine whether a user has access to our system. These integrations are highly flexible and adapt to your existing infrastructure, including your authentication system, parameters, URL structure, and response formats.

Options#

We support two types of callback integrations: basic access validation, and access validation with user data.

Basic Access Validation#

A callback that simply indicates whether a user can log in to the application or not. This provides a simple yes/no response based on the user's access status.

Access Validation with User Data#

A callback that not only indicates whether the user has access but also returns additional information such as user data, activated services, or other relevant details. This allows for more granular access control and user provisioning.

Examples#

The following examples demonstrate both types of callback integrations. In these scenarios, we assume that the integration validates the user with a NID number, and the user with ID number 12345678J exists as a customer, while 87654321X does not.

Example 1: Basic Access Validation (Yes/No)#

This example shows a simple callback that returns user information if the user exists, or an error if they don't.

Request for existing user:

GET https://xxx.net/getUser?nid_number=12345678J&token=abcdefgh456789ijkl

Response: HTTP 200

{
    "ID": "12345678J",
    "status": "premium"
}

Request for non-existing user:

GET https://xxx.net/getUser?nid_number=87654321X&token=abcdefgh456789ijkl

Response: HTTP 401

{
    "status": "Not found"
}

Example 2: Access Validation with Active Services#

This example demonstrates a callback that returns whether the user has active services and provides details about their policies and services.

Request for existing user:

GET https://yyy.com/api/services
Authorization: Bearer TOKEN
Content-Type: application/x-www-form-urlencoded

dni=12345678J

Response: HTTP 200

{
    "contracted": "Y",
    "policies": [
        {
            "policy": "0000012345678",
            "services": "ML"
        },
        {
            "policyCertificate": "0000012349647",
            "services": "ML-MD"
        }
    ]
}

Request for non-existing user:

GET https://yyy.com/api/services
Authorization: Bearer TOKEN
Content-Type: application/x-www-form-urlencoded

dni=87654321X

Response: HTTP 404

{
    "contracted": "N",
    "policies": []
}