Skip to main content
This page provides detailed definitions of response fields for the GET/Submission API.

Field Inclusion Rules

Fields in a GET/Submission response are included in the response object only when they have a value. A field without a value is not returned as null; the key itself is omitted.
  • The response for a submission with no stored email has no email key.
  • The image object is included only when at least one of idImage, idBackImage, selfieImage, or addressImage exists. If none exist, the image object itself is absent.
  • Most optional fields, such as userid, updated_at, kyc_result_at, pending_at, tokenId, applicant_id, recognition_score, argos_score, and duplicated_information, follow the same rule.
Before accessing nested fields such as Items[0].image.idImage, check that the parent field exists.

Response Field (ID document)

Signals Object and Confidence

Auxiliary data generated during submission processing is returned under the signals object.

Confidence Object (signals.confidence) ⭐ NEW

Object that provides OCR recognition confidence scores. It includes a confidence score (0.0 ~ 1.0) per category. These values correspond to the per-field confidence shown in the dashboard submission detail view.

signals.confidence.finalData

Confidence scores for the final data used in ARGOS Score calculation.

signals.confidence.ocrData

Confidence scores for OCR-extracted data.

signals.confidence.ocrExtractedData

Confidence scores for data extracted directly from the source by the OCR engine.
The ocrExtractedData property is not returned for Korean national ID cards and driver’s licenses.
Additional fields extracted by the OCR engine may be included.
  • All confidence values are numbers in the range 0.0 ~ 1.0.
  • Fields are included conditionally based on data presence and confidence values.

Response Field (Knowledge-based)

Camera Process Type Details

Additional data generated during the process is returned under the signals object. The type field in the signals.cameraProcessInfo array indicates the method used by the user to submit images at each process stage.
Process types that define how ID document images are captured.

1.1 ID document Front (ProcessIdCardFront)

Defines the method for capturing the front of an ID document.

1.2 ID document Back (ProcessIdCardBack)

Defines the method for capturing the back of an ID document.
Process types that define how face images are captured for authentication.

2.1 ID document Face Authentication (IdDocumentFace)

Defines the method for capturing a face image to compare with the face registered on the ID document.

2.2 Knowledge-Based Face Authentication (KnowledgeFace)

Defines the method for capturing a face image to compare with previously registered face information.
The signals.cameraProcessInfo array sequentially records all process stages the user went through during submission. You can track the user’s submission journey through the start time, end time, and error information of each process.

Getting Started

The ID check API is a solution designed to help enterprise clients manage KYC (Know Your Customer) and AML (Anti-Money Laundering) processes more systematically and efficiently. This API supports seamless integration with existing systems and provides features to securely handle and manage user data.

Overview

Monitor ARGOS ID check’s KYC process status changes in real-time. Receive instant updates through webhooks.