PATCH/Submission

  • Modify the information of single-submission data.

  • The modified data can be edited again, but cannot be restored to its original state.

Request URL

  • You must provide the URL and x-api-key.

curl -X PATCH "https://rest-api.argosidentity.com/v3/submission" \
-H "x-api-key: {yourAPIKey}" \

Sample Request 1

  • This is a sample request to modify the submitted KYC (Know Your Customer) data.

curl --location --request PATCH 'https://rest-api.argosidentity.com/v3/submission' \
--header 'x-api-key: {yourAPIKey}'

Sample Request 2

  • This is a sample data for a modification request submission. (Body)

{
  "submissionId": "6xx28lo115832",
  "admin": "yourAdmin@sample.com",
  "data" : 
		{
			"idType": "drivers_license", 
			"issuingCountry": "KOR", 
			"fullName": "hong kil dong", 
			"gender": "male", 
			"birthDate": "1999-11-31", 
			"nationality": "USA" , 
			"kycStatus": "approved", 
			"issueDate": "2017-10-19", 
			"expireDate": "2027-10-18"
			"identityNumber": "991131-1111111",
			"documentNumber": "05-167-U0815",
			"serialNumber": "07PN10"
		}
}

Sample Response

  • This is sample data that can be used to verify the completion of the modification.

{
	"message": "success to edit.",
}

Input Data

  • An explanation of the parameters for modifying KYC data (submission).

  • It is essential to strictly adhere to the specified Value format.

Using Encryption Option for Input Data

June 21, 2024

When using the encryption option, both input and output require bidirectional encryption/decryption.

Encrypt the Request Body for API Request:

body: encrypt({
    email: 'string',
    fullName: 'string',
    issuingCountry: 'string',
    birthDate: 'string',
    ...
})

Output Data

  • List of data returned when modifying KYC data (submission).

Using Encryption Option for Output Data

Return the encrypted result in the data property within the Body object.

Example:

response : {
   body : {    
       "data": "encrypted-string",    
       "isEncrypted": true
   }
}

Last updated