Check responses will be returned in the standard JSON API format. Fields are as follows:
Parameter | Description | Notes |
| ​ | ​ |
| An overall recommended result for the check | 'Pass', 'Refer' or 'Fail' |
| The country the check was carried out in | ​ |
| ​ | Currently for internal use |
| The ID3 profile used to carry out the check | ​ |
| The name of the profile | ​ |
| ​ | Currently for internal use |
| ​ | Currently for internal use |
| ​ | Currently for internal use |
| An array of objects, each representing the results of a check against a particular database | See below for details |
| A numeric result score for the check | ​ |
| Timestamp for when the check was carried out | ​ |
| ​ | Currently for internal use |
| ​ | For standards compliance; will always be 'id3-check' |
The API returns an array of result objects, one for each database check which has been performed as part of the check. Different check levels will perform different database checks. Fields are as follows:
Parameter | Description | Notes |
| A result for this particular check. | Match, Nomatch etc |
| If provided, was there a match on the date of birth? | ​ |
| An array of objects containing comments provided on this particular check. These are specific to the check being performed and are used to provide information such as missing data. Fields are 'code' and 'description'. | ​ |
| If provided, was there a match on the date of birth? | ​ |
| Text description of this particular check | ​ |
| If provided, was there a match on the forename? | ​ |
| Check code | Currently for internal use |
| The title of this particular check | ​ |
| Result indicating whether this particular check has 'passed' | ​ |
| List of sanctions / PEPs, if this particular result contains that information | ​ |
| If provided, was there a match on the surname? | ​ |