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/Submission/applicantId
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

​
applicant_id
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 NameDescriptionData Type
submission_idUnique identifier of the duplicate submissionString
duplicated_informationA 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
emailEmail address linked to the duplicate submissionString
This API allows you to efficiently monitor and manage duplicated KYC submissions.