Du er ikke logget på
Identity Validation API

On this page you will find information about Geomatic's Identity Validation API.

Please also read this section to learn about authentication.

API Specification

The purpose of the Identity Validation API is to provide an easy solution to implement electronic identity validation/verification. In this section you can read about how to create the request to the web service and what response you will get back.

Identity Validation Request

The identity validation API takes some input and returns an identity validation response containing validation codes for that input.

You can perform a call to the identity validation API by making a GET request of the form:

https://apps.conzoom.eu/api/v1/eidv/validate?in_adr={adr}&in_name={name}&in_dob={dob}&in_person_id={pid}

Query String Parameters

You are able to provide the following query parameters:

To be able to validate a person you need as a minimum to provide one of the following combinations of input:

Identity Validation Response JSON

For each request, the identity validation service returns a JSON object containing the validation codes for the input. The codes will never be null, and will always have a value.

The response of a validation request will look like this:

    {
        "person_found": {boolean},
        "name_adr_protected": {boolean},
        "person_status": {person_status_code}
        "adr": {address_validation_code},
        "adr_match_level": {address_match_level},
        "name": {name_validation_code},
        "dob": {dob_validation_code},
        "person_id": {person_id_validation_code}
        "phone_1": {phone_validation_code}
        "phone_2": {phone_validation_code}
    }

The person_found property will contain a boolean value to indicate whether we could find the person or not. The possible values and their meaning are listed below:

The name_adr_protected property will contain a boolean value to indicate whether the person is name and address protected. For protected persons it's not possible to obtain their current name and address. The possible values and their meaning are listed below:

The person_status property will contain the status of the matched person - as provided by the underlying registry.

The adr property will contain a validation code for the input address provided in the request. The possible values and their meaning are listed below:

For in_extended_address_match=true we return the adr_match_level code indicating at which level a fuzzy_match (or match) from property adr has been matched. For adr=match this will always be suite. For fuzzy_match it will be one of the following.

The name property will contain a validation code for the input name provided in the request. The possible values and their meaning are listed below:

The dob property will contain a validation code for the date-of-birth provided in the request. The possible values and their meaning are listed below:

The person_id property will contain a validation code for the person identity number in the request. The possible values and their meaning are listed below:

The phone_1 and phone_2 properties will contain a validation code for the phone numbers provided. The possible values and their meaning are listed below: