Overview
Use this method to retrieve information extracted from the applicant’s documents, provided the applicant is approved. The method aggregates data from all documents and ignores verification levels.
To retrieve information recognized only from approved documents, set the forApprovedImages parameter to true. In this mode, the method works exclusively for approved applicants and approved documents.
Important
If the applicant is in the Rejected or Resubmission requested status, the method returns an error.
Request examples
// This request returns data only from approved applicant documents.
curl -X GET \
'https://api.sumsub.com/resources/applicants/67b3659550a9ed51c777daa9/info/idDocs?forApprovedImages=true'
// This request returns data from all applicant documents, independent of their approval status.
curl -X GET \
'https://api.sumsub.com/resources/applicants/67b3659550a9ed51c777daa9/info/idDocs'
Response explained
The response is a JSON object containing information extracted from the applicant's documents. Its structure and content match the format of the idDocs array returned by the Get applicant data method.
idDocs element fields
idDocs element fieldsThe table below describes the fields that represent data extracted from the applicant’s documents.
| Field | Type | Description |
|---|---|---|
idDocType | String | Type of document that is specified in the level to be provided for verification. For example, PASSPORT, UTILITY_BILL, VEHICLE_REGISTRATION_CERTIFICATE, and so on.See the lists of supported document types and supported company document types for details. |
ocrDocType | String | Specifies the document subtype as a full type identifier (for example,
Additional variations may be the following:
If the subtype cannot be determined, the field is returned empty. ⚠️ Note: This field is intended for analytical purposes only. Do not rely on its value for critical business logic, as it may not always be determinable with full accuracy. |
country | String | Alpha-3 code (for example, DEU, GBR, ARG, and so on) of the country where the document was issued. |
firstName | String | Applicant first name in the original language as it is in the document. |
firstNameEn | String | Automatic transliteration of the applicant first name into Latin characters. |
middleName | String | Applicant middle name in the original language as it is in the document. |
middleNameEn | String | Automatic transliteration of the applicant middle name into Latin characters. |
lastName | String | Applicant last name in the original language as it is in the document. |
lastNameEn | String | Automatic transliteration of the applicant last name into Latin characters. |
aliasName | String | Alternative first/last name. |
title | String | A word or abbreviation placed before a person's name to indicate their profession, social rank, academic degree, or form of address (Dr, Mr, Ms, Prof, and so on). |
issuedDate | Date | Date when the identity document was issued (format YYYY-MM-DD). |
issueAuthority | String | Official name of the authority that issued the document. |
issueAuthorityCode | String | Code of the Issuing Authority that is in charge of issuing the uploaded document. |
termless | Boolean | Indicates whether the document is marked as valid indefinitely (true) or not (false); see the validUntil field for the expiration date.⚠️ For now, "validUntil": "2099-01-01" will be returned for documents marked as indefinite ("termless": true). This is a temporary behavior and will be discontinued in the coming months. |
validUntil | Date | Date when the document validity expires. |
extendedValidUntil | Date | Additional date when the document validity expires, in case the document validity has been extended (format: YYYY-MM-DD, for example, 2029-05-20).ⓘ Returned only if custom rules are applied to extend validUntil, or if country-specific document prolongation rules are in effect. |
number | String | Unique registration number of the document. |
additionalNumber | String | Usually, it is a sort of personal number. For example, DNI in Spain, CRP in Brazil, or ARC in Cyprus. |
dob | Date | Applicant date of birth (format YYYY-mm-dd, for example, 2001-09-25) as it is specified in the document. |
address | Object | Includes the applicant address details. |
ethnicity | String | Indicates the applicant's ethnic background. Presented as a custom value. |
mrzLine1 | String | A line of MRZ (machine-readable zone) from the document. Additional lines, such as mrzLine2 and mrzLine3, may also be present if available. The number indicates the line position in sequential order. |
nfcInfo | Object | Includes the data extracted from the NFC chip of an identity document. |
address attributes
address attributesThe following table explains the address attributes that represent 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. |
subStreetEn | String | Automatic transliteration of the additional information related to the street into Latin characters. |
street | String | Street name. |
streetEn | String | Automatic transliteration of the street name into Latin characters. |
state | String | State, region, district, county or another territorial entity inside a country. |
stateEn | String | Automatic transliteration of the territorial entity into Latin characters. |
stateCode | String | Applicant state code based on the address. A list of state codes is based on the ISO 3166-2 (for example, TR-34, AD-07). |
buildingNumber | String | Building number. |
town | String | City, town, or another settlement. |
townEn | String | Automatic transliteration of the settlement into Latin characters. |
postCode | String | Address postal code. |
country | String | Alpha-3 country code (for example, DEU, GBR, ARG, and so on). |
formattedAddress | String | Address in a human readable format. For example, Design Offices, Philipsbornstraße 2, 30165 Hannover, Germany. |
source | String | Address data source. This information can be obtained from Applicant data, Proof of Address, and Geo as PoA. |
nfcInfo attributes
nfcInfo attributesThe following table explains the nfcInfo attributes representing the data extracted from the NFC chip of an identity document.
| Field | Type | Description |
|---|---|---|
fullMrz | String | Contains the full Machine-Readable Zone (MRZ) data from the ID document. |
imageId | String | Unique identifier of the image that represents the uploaded document. |
Response examples
If the request is successfully sent and processed, you will get a response like the one below.
{
"idDocs": [
{
"idDocType": "ID_CARD",
"country": "DEU",
"firstName": "CHRISTIAN",
"firstNameEn": "CHRISTIAN",
"lastName": "SMITH",
"lastNameEn": "SMITH",
"aliasName": "BROOKS",
"validUntil": "2028-09-04",
"number": "LGXX359T8",
"dob": "1989-07-16",
"mrzLine1": "IDD<<LGXX359T88<<<<<<<<<<<<<<<",
"mrzLine2": "8907167<2809045D<<<<<<<<<<<<<8",
"mrzLine3": "SMITH<<CHRISTIAN<<<<<<<<<<<<<<",
"nfcInfo": {
"fullMrz": "MRZ IS HERE",
"imageId": "IMAGE ID IS HERE"
}
}
]
}
If the request fails, you will receive an HTTP response containing an error code along with a message explaining the error. For example:
{
"code": 400,
"description": "Applicant should be not in rejected state",
"correlationId": "955bce80ffb06f470d4bd7665f02f2df"
}