Data Injection is a method to update information for an existing submission via a separate path. This process replaces existing category data with new information.
To perform an Injection, a submission must first be created via Liveform.
Additional information sent via Query Strings is included in the response data when calling the API. This enables the following functionalities:
Query String options can be applied using the ARGOS ID Check Liveform. All Query String values must be URL-encoded.
https://form.argosidentity.com/?pid={project_Id}
https://form.argosidentity.com/?pid={project_id}&action=addveri&sid={submission_id}
https://form.argosidentity.com/?pid={project_id}&encrypted={encrypted_values}
The Injection URL with encryption method are required to encrypt the sid and action parameters.
https://form.argosidentity.com/?pid={project_id}&encrypted={encrypted_values} (O)
(X) example functions similarly to an unencrypted addveri (Address Verification) action URL, ignore encrypted parameter options.
Please refer to this link for encryption methods.
Unique project identifier.
Unique submission identifier. sid
must also be encrypted in order to use any encrypted parameter.
Injection option action, use addveri
. action
must also be encrypted in order to use any encrypted parameter.
Custom option field #1.
Custom option field #2.
Custom option field #3.
Must be encrypted. Custom unique user identifier.
Must be encrypted. Set the risk for IP-based routing services. As of now, vpn
,proxy
and tor
parameters are supported. There is no space between the comma and the option name in each option. This option is paired with the ipRiskDurationHours
option.
Must be encrypted. Access can be directly restricted within a specified hour if the system determines that an IP address poses a risk. Risky IP addresses will be immediately blocked in set hours. It must be used with ipRiskCategory
.
Must be encrypted. The option to prevent users from continuing if their address is distant from their IP. Currently, ipGeo
is only available. This option is paired with the distanceMaxDistanceKm
.
Must be encrypted. Can set a distance between the entered address and the IP-based address. If distanceCheckSource
is set without distanceMaxDistanceKm
, It must be used with distanceCheckSource
.
Must be encrypted. In order to forbid a country from being blacklisted in the dashboard, it must be set to true. The default value is false.
The address inputted in the injection is a concern for the blacklist countries.
IP location and submitted country are not relevant.
Rejection Code | Description |
---|---|
ipRisk_failCategory | Detection of selected ipRisk Categories. |
distanceChecks_ipGeo | The distance exceeds the set killomiter, as indicated by ipGeo. |
blackliskCountries | Unable to perform injection due to the presence of blacklistCountries. |
Error Code | Description |
---|---|
Invalid required | Missing required parameter. |
Required field is missing | Missing one or more of the following: sid, pid, or address data. |
Invalid submissionId | The provided sid does not exist. |
Invalid projectId | The provided pid does not exist. |
Error in injecting address | Undefined, unspecified error occurred during address injection. |
Refer to Data Injection of Webhook section.
ipRiskCategory
that was applied and the risk that was detected, displays the message: “VPN/Proxy Detection, Please disable VPN or proxy and try again with a regular network connection.”distanceCheckSource
and the distance is over than the specified distance in km, Displays the message: “Address Verification Failed, Please verify your address or try again on a network near your residence.”There is no webhook for IP risk detection. However, if the distance check fails or a blacklist country is detected, a webhook will be generated. Reference the responses. Refer to Data Injection of Webhook section.
This guide helps you effectively utilize the Data Injection feature and Query String options in ID check to flexibly manage and customize the ID check process.