This creates a new request and optionally sends notifications to your users
Getting started with Digio Rest Apis
|
HTTP Basic
Send
Authorization in header containing the word Basic followed by a space and a base64 encoded string of username:password.
|
Create Request
Request Body Params (application/json)
Create a new request in DigiStudio from a standard or custom template
{
"customer_identifier": "someone@gmail.in",
"customer_name": "Abhishek",
"template_name": "FACEMATCH-VERIFY",
"notify_customer": true,
"expire_in_days": 10,
"generate_access_token": true,
"reference_id": "1234",
"transaction_id": "ABCW233",
"generate_deeplink_info": true
}
Email/mobile phone number of the customer to which the KYC request is sent.
If true, a notification is sent to the customer on their email/mobile phone. Recommendation: if using only SDK then pass false in notify_customer param
➔ Sends an SMS/Whatsapp notification if the identifier is mobile number
➔ Name of the customer. Max length: 100
➔ Customer reference number (underscore or alphanumeric string supported). If not passed, one will be auto generated by Digio
➔ Unique identifier referring to transaction (underscore or alphanumeric string supported). If not passed, one will be auto generated by Digio
➔ Name of KYC template created over dashboard to be used while creating the request.
Can be used to prefill form feilds or digilocker linked attributes in the KYC flow
Attributes using which additional documents can be fetched from digilocker(Not applicable for AADHAAR). E.g {"PAN":{"pan_number":"ABCDEF123","name":"Test name"}})
Attributes using which additional documents can be fetched from digilocker(Not applicable for AADHAAR). E.g {"PAN":{"pan_number":"ABCDEF123","name":"Test name"}})
Attributes using which additional documents can be fetched from digilocker(Not applicable for AADHAAR). E.g {"PAN":{"pan_number":"ABCDEF123","name":"Test name"}})
➔ Request Expiry in number of days => Default: 10 days, After expiry user will not be able to proceed
⮕ [ Array of signer objects ]
Email address or mobile of user
➔ Signing reason for user from whom signature is requested
➔ 'aadhaar' : sign using aadhaar. [default] 'dsc' : sign using DSC 'electronic' : Screen pad based signature (slate signature)
➔ mode of signature, if sign_type is electronic
➔ Name of signer
Signer tag as mentioned in the template created over dashboard.
Additional sign features added upon document signing
⮕ [ Additional sign features added upon document signing ]
➔ geo_location: if geolocation is required
➔ geo location with address
➔ pass true if geo location is optional
Details of Estamps, Quantities to be consumed and other merge details like
Map of tag names and quantities to be attached. Tag names should be without spaces
Note : Do not pass any special character or space in E-stamp tag name. Available tag names can be checked on dashboard -> E-Stamping section
➔ note on estamp page
➔
➔
Default false, if you need an access token then pass this. If allowed for other input details, will receive an access_token object in response(For SDKs only).
Reverse Penny Drop Config ID
As Part of the Customer Onboarding Journey Clients can charge their customer. Amount to be charged can be configured here.
E Stamp Certificate ID consumed during document creation
Flag indicating whether to generate Deep link Info
curl -X POST "https://api.digio.in/client/kyc/v2/request/with_template" \
-H 'accept: application/json'
Unique identifier referencing a request.
Time of creation of a request.
➔ Status of the request. “requested” immediately post creation
Customer email/phone number as passed in the request.
LIST of details of steps configured in workflow along with approved/reject status
⮕ [ LIST of details of steps configured in workflow along with approved/reject status ]
Step Request ID
Action Reference
➔
➔
file Id
sub file Id
equivalent to Digilocker request ID or Form request ID or reverse penny drop request ID
Result Obtained after validation
Completion Time
➔
➔
➔
➔
Flag that identifies whether the processing of the request is done or not
Configurable rules that determines how many retries the request is allowed to do
Internal reference ID as passed in the request.
Data passed in the request that is displayed on the dashboard, usually to help an agent make a decision.
Data passed in the request that is displayed on the dashboard, usually to help an agent make a decision.
As passed in the request. Generated by the system and returned if not passed.
The name of the customer
No. of days after which the KYC request will expire.
States if there is any reminder registered.
Only applicable while creating sign request when generate access token value is passes as “true”
'yyyy-mm-dd hh:mm:ss': Timestamp of generation
'yyyy-mm-dd hh:mm:ss': Timestamp of update
Unique identifier of the parent entity the access token belongs to
Unique identifier referencing an access token
DateTime at which the access token expires. New token can be generated when expired with the access token generation API mentioned in the document.
Name of the workflow.
error messages generated
A flag indicating that the file should automatically move on the Approved State or not
Name of the auditor
Unique identifier referencing auditor.
Additional Validation Required
➔
Attributes required for validation
➔
Confidence below which the match fails
Plugin to be invoked upon KYC request reaching a particular status (can be configured by the client)
Unique identifier for Workflow template created over dashboard (generated by Digio, e.g: KTP12345678)
Deep intent meta for reverse penny drop
Deep Intent Url
Deep QR Url
Details about the exception. Usually contains the exception id for reference.
Error code
Description of the error