Time	Status	User Agent
Retrieving recent requests…

Overview

Use this method to retrieve Non-Doc verification results.

Request example

curl -X GET \
     'https://api.sumsub.com/resources/checks/latest?applicantId=67346d0623c63349989d32bb&type=E_KYC_CHECK' \
     -H 'accept: application/json' \
     -H 'X-App-Token: <your-app-token>' \
     -H 'X-App-Access-Sig: <your-signature>' \
     -H 'X-App-Access-Ts: <unix-timestamp>'

Response explained

The response represents a list of checks.

Root variables

The root variables (in the checks array) are the core check result data items. Some of them may include nested attributes and element fields.

Field	Type	Description
`id`	String	Unique identifier of the check.
`answer`	String	Verification result: `GREEN` — verification passed successfully. `YELLOW` — verification is still in progress; the applicant has not completed all required steps. `RED` — verification indicates a high-risk result. The applicant data does not match the database record, or no data was found. See the response examples for more information. `ERROR` — verification was not completed because the service was unavailable or the system failed to process the response.
`inputDoc`	Object	Data used as input for the database verification.
`checkType`	String	Type of verification check performed.
`extractedDoc`	Object	Data retrieved from the external source. It may be absent if no data was received.
`createdAt`	Date	Date and time (UTC) of the latest check result.
`ekycCheckInfo`	Object	May include face-matching results from an external database and Non-Doc verification metadata. Can be empty.
`violations`	Array of strings	High-risk indicators, returned when `answer` is `RED`.
`databasePersonCheckInfo`	Object	Contains verification results and metadata for a database identity verification. ⚠️ Currently available only for German eID Verification.

`inputDoc` attributes

The following table explains the inputDoc attributes representing the data provided by the applicant.

Field	Type	Description
`idDocType`	String	Type of the document or data provided for verification. For example, `TAX_PAYER_NUMBER_DOC`, `ID_CARD`, `PASSPORT, DRIVERS`.
`country`	String	Alpha-3 country code (for example, `DEU`, `GBR`, `ARG`).
`firstName`	String	First name provided by the applicant.
`middleName`	String	Middle name provided by the applicant.
`lastName`	String	Last name provided by the applicant.
`number`	String	Identification number provided by the applicant.
`additionalNumber`	String	Additional identification number provided by the applicant.
`dob`	Date	Date of birth provided by the applicant, in format `YYYY-mm-dd` (for example, `2001-09-25`).
`address`	Object	Address provided by the applicant.
`phone`	String	Phone number provided by the applicant

`extractedDoc` attributes

The extractedDoc object includes the data obtained from the external source during Non-Doc verification.

Field	Type	Description
`country`	String	Alpha-3 country code (for example, `DEU`, `GBR`, `ARG`).
`idDocType`	String	Type of the identification number or document, retrieved from the external source. For example, `TAX_PAYER_NUMBER_DOC`, `ID_CARD`, `PASSPORT`, `DRIVERS`.
`number`	String	Identification number.
`firstName`	String	Applicant full name.
`middleName`	String	Applicant middle name.
`lastName`	String	Applicant last name.
`aliasName`	String	Alternative first/last name or additional name.
`dob`	Date	Applicant date of birth (format `YYYY-mm-dd`, for example, `2001-09-25`) as it is specified in the document.
`gender`	String	Gender of the applicant (`M`, `F`, or `X`).
`nationality`	String	Applicant country of origin. Presented as an ISO 3166-1 alpha-3 country code (for example, `DEU`, `GBR`, `ARG`).
`placeOfBirth`	String	Applicant place of birth. This can be a city, a town or another settlement type. There is no length limit for this field.
`stateOfBirth`	String	State, region, district, county or another territorial entity of birth inside a country, if applicable.
`countryOfBirth`	String	Applicant country of birth. Presented as an ISO 3166-1 alpha-3 country code (for example, `DEU`, `GBR`, `ARG`).
`tin`	String	Taxpayer identification number that is unique to each taxpayer.
`issueDate`	Date	Date when the identity document was issued (format `YYYY-MM-DD`).
`validUntil`	Date	Date when the document validity expires (format `YYYY-MM-DD`).
`issueAuthority`	String	Official name of the authority that issued the document.
`issueNumber`	String	Unique number assigned to the document by the issuing authority.
`category`	String	Category of a document, visa, or identification number.
`phone`	String	Applicant phone number.
`email`	String	Applicant email address.
`addresses`	Array of objects	Includes data objects containing the applicant address details retrieved from the external database.
`additionalFields`	Array of objects	A collection of key-value pairs, representing additional information retrieved from the external database. See response examples for more details.
`images`	Array of objects	ID of selfie or document image obtained from the external database. See response examples for more details.

`addresses` element fields

The following table explains the addresses element fields containing the applicant address details.

Field	Type	Description
`buildingName`	String	Building name.
`flatNumber`	String	Flat or apartment number.
`subStreet`	String	Additional information related to the street. This could be a house number or any other details.
`street`	String	Street name.
`state`	String	State, region, district, county or another territorial entity inside a country.
`buildingNumber`	String	Building number.
`town`	String	City, town, or another settlement.
`postCode`	String	Address postal code.
`country`	String	Alpha-3 country code (for example, `DEU`, `GBR`, `ARG`).
`formattedAddress`	String	Address in a human readable format. For example, `Design Offices, Philipsbornstraße 2, 30165 Hannover, Germany`.
`source`	String	Always `externalDb`. Indicates that the address was retrieved from the external database.

`additionalFields` element fields

An array of key-value pairs providing non-standard additional information.

Example:

{
  "name": "fileNumber",
  "value": "000323042233"
}

📘
Note
Refer to the response examples for a specific solution to obtain the list of relevant additional fields and their descriptions.

`ekycCheckInfo` attributes

The following table explains the ekycCheckInfo attributes.

Field	Type	Description
`externalFaceMatch`	Boolean	Indicates that the face matching was performed in the external database.
`faceMatchAnswer`	String	External database face match verification results: `GREEN` — applicant selfie matches the photo from the external database. `YELLOW` — probability of a selfie match is not high enough to be considered successful. The user needs to take a new selfie. `RED` — applicant selfie does not match the photo in the external source. `ERROR` — no photo available in the external database, or the system failed to process the face match verification. `IGNORED` — face match verification has been skipped.
`faceMatchScore`	Double	Numerical confidence score of the face match result in the range from `0` to `1`. Higher value indicates a higher probability of a match.
`selfieImageId`	Integer	ID of the applicant selfie image, used for face match verification.
`confirmationType`	String	Confirmation type, if available: `oAuth` — Non-Doc verification confirmed by authorization in an external service, such as a bank account, national digital identification system, and so on. `eID` — Non-Doc verification confirmed by NFC verification using the eID card. `otp` — Non-Doc verification confirmed by OTP-code.
`confirmationId`	String	Unique identifier of the eKYC confirmation session.
`skipped`	Boolean	Indicates if the Non-Doc verification step was skipped in the SDK. This field is only returned if skipping the Non-Doc step is permitted in the Non-Doc settings.

`databasePersonCheckInfo` attributes

The databasePersonCheckInfo object includes verification results and metadata for database verification.

Field Type Description

Field	Type	Description
`processingEvents`	Array of objects	Timeline of events captured throughout the verification lifecycle. ⚠️ Currently available only for German eID Verification.

processingEvents

Array of objects

Timeline of events captured throughout the verification lifecycle.

⚠️ Currently available only for German eID Verification.

`processingEvents` attributes

The processingEvents object represents an individual audit entry within the verification lifecycle.

Field	Type	Description
`event`	String	Unique identifier of the event (for example, `eidGeneralError`, `eidCardLocked`).
`date`	Date	Date and time (UTC) of the event.

`violations` indicators

Indicator	Description
`ACCOUNT_NOT_FOUND`	Provided account details were not found in the records.
`ACCOUNT_NOT_OPEN`	Provided account is closed, dormant, or inactive.
`ACCOUNT_TYPE_MISMATCH`	Provided account type does not match the database record.
`ADDRESS_MISMATCH`	Provided address doesn't match the records in external sources.
`AUTHENTICATION_FAILED`	User cancelled the authentication process or denied permission to share data during the OAuth flow..
`BDATE_MISMATCH`	Provided date of birth does not match the database record.
`DATA_NOT_FOUND`	Data not found.
`DEAD`	Deceased person.
`DOC_EXPIRED`	Applicant identification document expired.
`EXTERNAL_DB_SUSPICIOUS`	External database returns data that appears unusual, inconsistent, or flagged for potential fraud.
`GENDER_MISMATCH`	Provided gender does not match the database record.
`ID_NUMBER_MISMATCH`	Provided identification number does not match the database record.
`INVALID_DOC_NUMBER`	Invalid identification or tax number.
`INVALID_ID_STATUS`	Document or tax status is invalid.
`NAME_MISMATCH`	Provided full name does not match the database record.
`NOT_ENOUGH_DATA`	Insufficient data available in the external source to complete verification.
`PERSON_IS_MINOR`	Person is underage.
`SELFIE_MISMATCH`	Provided selfie doesn’t match the photo in the external source.
`VERIFICATION_REQUIREMENTS_NOT_MET`	There is insufficient data matching the external source, or some verification requirements have not been met.

Response examples

If the request is successfully sent and processed, you will get a response like one of those below.

{
  "checks": [
    {
      "answer": "GREEN",
      "checkType": "E_KYC_CHECK",
      "createdAt": "2024-03-21 11:39:23",
      "id": "6fe0ec3b-c6d8-4c53-afc6-f33751dbf1c2",
      "inputDoc": {
        "idDocType": "TAX_PAYER_NUMBER_DOC",
        "country": "BRA",
        "number": "07244434529"
      },
      "extractedDoc": {
        "firstName": "LUCAS OLIVEIRA",
        "aliasName": "MARIA LURDES",
        "gender": "M",
        "dob": "1991-01-15",
        "placeOfBirth": "BRASILEIRA",
        "additionalFields": [
          {
            "name": "registrationStatus",
            "value": "Regular"
          },
          {
            "name": "fatherName",
            "value": "JOHN DOE"
          }
        ]
      },
      "ekycCheckInfo": {
        "externalFaceMatch": true,
        "faceMatchAnswer": "GREEN",
        "selfieImageId": 118005011,
        "faceMatchScore": 0.9491729928035084
      }
    }
  ]
}

{
  "checks": [
    {
      "answer": "YELLOW",
      "checkType": "E_KYC_CHECK",
      "createdAt": "2025-11-06 21:39:24",
      "id": "faf3469c-7320-4533-8d78-901072fb8f5b",
      "inputDoc": {
        "idDocType": "OTHER",
        "country": "DNK"
      },
      "ekycCheckInfo": {
        "confirmationId": "TX0zGu2IT6YQYkMcMXTYorh8",
        "confirmationType": "oAuth"
      }
    }
  ]
}

{
  "checks": [
    {
      "answer": "RED",
      "checkType": "E_KYC_CHECK",
      "createdAt": "2026-02-06 10:35:15",
      "id": "4e45a3ca-ab7f-4d45-a2b8-91ea7ebd5e4e",
      "inputDoc": {
        "idDocType": "TAX_PAYER_NUMBER_DOC",
        "country": "NGA",
        "number": "00000000000"
      },
      "ekycCheckInfo": {},
      "violations": [
        "DATA_NOT_FOUND"
      ]
    }
  ]
}

{
  "checks": [
    {
      "answer": "ERROR",
      "checkType": "E_KYC_CHECK",
      "createdAt": "2025-02-05 12:46:04",
      "id": "6bf059dc-03d6-4c4c-96d6-d4fec6245def",
      "inputDoc": {
        "idDocType": "ID_CARD",
        "country": "UZB",
      },
      "ekycCheckInfo": {}
    }
  ]
}

If the request fails, you will receive an HTTP response containing an error code along with a message explaining the error. For example:

{
  "code": 404,
  "correlationId": "b77f6b1246aa8bd5a2032f66ba514dae",
  "description": "Applicant with id 6985c3c5ef3ef5fe99f5605d not found"
}

The following pages provide response examples per country:

Overview

Request example

Response explained

Root variables

inputDoc attributes

extractedDoc attributes

addresses element fields

additionalFields element fields

Note

ekycCheckInfo attributes

databasePersonCheckInfo attributes

processingEvents attributes

violations indicators

Response examples

200200

404404

`inputDoc` attributes

`extractedDoc` attributes

`addresses` element fields

`additionalFields` element fields

`ekycCheckInfo` attributes

`databasePersonCheckInfo` attributes

`processingEvents` attributes

`violations` indicators