Data Injection - ARGOS Identity

If the injection contains cf1 ~ cf3, the webhook will respond with cf1 ~ cf3. However, the injection webhook response does not include the cf1 ~ cf3 information, as it has already been included in the submission.

{
    "webhook_trigger": "injection",
    "action": {
        "type": "address",
        "created_at": "YYYY-MM-DD-HH-MM-SS-ZZZ"
    },
    "submission_id": "{submission_id}",
    "email": "email@email.com",
    "kyc_status": "approved",
    "applicant_id": "{applicant_id}",
    "userid": "{userid}",
    "cf1": "{custom_field1}",
    "cf2": "{custom_field2}",
    "cf3": "{custom_field3}",
    "tokenId": "{token_id}"
}

webhook_trigger

string

Webhook event type - injection indicates a data injection event.

action

object

An object containing information about the data injection operation.

Show properties

type

string

The type of data being injected (e.g., “address”).

created_at

string

The UTC timestamp when the data injection operation was executed (ISO 8601 format).

failCode

string

Show the failure cause as a code if the injection was unsuccessful.

submission_id

string

Unique identifier for each KYC submission.

kyc_status

string

Result of the KYC.

duplicated_information

string

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 address of the KYC submitter.

applicant_id

string

A unique identifier assigned to detect duplicate submissions, provided only when the KYC status is approved.

userid

string

Unique identifier for the KYC submitter as defined by the client.

cf1

string

Value of custom field 1.

cf2

string

Value of custom field 2.

cf3

string

Value of custom field 3.

tokenId

string

Token ID used for submissions in private mode live forms.

Webhooks