GET/Submission/applicantId

Notes

applicant_id is generated by comparing five data points: name, date of birth, gender, nationality, and selfie.
If no duplicates exist, only a single approved submission will be returned.
Ensure the applicant_id is first obtained using the GET/submission API.
If there is no comparable data, a random applicant_id is generated.

1. Endpoint

GET https://rest-api.argosidentity.com/v3/submission/applicant

2. Authentication

Include the API key in the x-api-key header:

x-api-key

x-api-key: {yourAPIKey}

3. Request Parameters

string

required

Unique identifier assigned to detect duplicate submissions (only for approved KYC submissions).

4. Request Example

GET/Submission/applicantId

curl --location --request GET 'https://rest-api.argosidentity.com/v3/submission/applicant?applicant_id={applicant_id}' \
--header 'x-api-key: {yourAPIKey}'

5. Response

5-1. Success Response

result.json

[
    {
        "submission_id": "{submission_id1}",
        "duplicated_information" : "{duplicated_information}",
        "email": "{email1}",
    },
    {
        "submission_id": "{submission_id2}",
        "duplicated_information" : "{duplicated_information}",
        "email": "{email2}"
    },
    {
        "submission_id": "{submission_id3}",
        "duplicated_information" : "{duplicated_information}",
        "email": "{email3}"
    }
]

5-2. Response Data

Field Name	Description	Data Type
`submission_id`	Unique identifier of the duplicate submission	String
`duplicated_information`	A unique ID is generated based on name, date of birth, gender, and nationality for duplicate checks. (*Always generated when all four criteria are provided.)	String
`email`	Email address linked to the duplicate submission	String

This API allows you to efficiently monitor and manage duplicated KYC submissions.

⌘I

Overview

API Reference

GET/Submission/applicantId

1. Endpoint

2. Authentication

3. Request Parameters

4. Request Example

5. Response

5-1. Success Response

5-2. Response Data

​1. Endpoint

​2. Authentication

​3. Request Parameters

​4. Request Example

​5. Response

​5-1. Success Response

​5-2. Response Data

1. Endpoint

2. Authentication

3. Request Parameters

4. Request Example

5. Response

5-1. Success Response

5-2. Response Data