Call this API to get Forms Data Request Details
Note : Copy the CURL only after filling the input parameters
Call this API to get Forms Data Request Details
Note : Copy the CURL only after filling the input parameters
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.
|
Call this API to Get Forms Data Request Details API
|
*
id
string
|
|||
|
Unique identifier referencing a request |
|||
curl -X GET "https://api.digio.in/client/form/{id}/response" \
-H 'accept: application/json'
Unique identifier referencing a request.
Customer email/phone number as passed in the request.
Unique identifier referring to form template to be used while creating the request.
Internal reference ID as passed in the request
As passed in the request. Generated by the system and returned if not passed.
f true, a notification is sent to the customer on their email/mobile phone.
Default: 10 days
➔ requested immediately post creation.
Name of the form Template
Description of the form Template
Detailed properties of the form
Detailed properties of the form
Detailed properties of the file
Detailed properties of the file
Unique ID to identify documents provided by Digio. This has to be passed for directly landing on this document within the website
true/false
➔ 'outbound': Sent request to sign 'inbound': Received request to sign
➔ 'requested': pending signature from at least one signing party 'completed': all signing parties have signed 'expired': at least one signing party did n’t sign prior to request expiry
(Note: Documents that “expired” without any signature, and hasn’t been accessed in a month will be archived. Documents successfully signed archived after an year audit trail is available for downloading)
Name of the file as provided by you
'yyyy-mm-dd hh:mm:ss': Timestamp of Document upload in IST
true/false
➔ 'Aadhaar','Electronic','DSC'
➔
Array of signing parties
Name of the signing party
➔ 'requested': pending signature from user 'signed': signed by user 'expired': user did not sign prior to request expiry
➔ 'self': Requested from self 'org': Requested from an Organization and signatory not assigned 'signatory': Requested from an Organization and signatory has been assigned
➔ 'aadhaar': signed to be signed using aadhaar 'dsc': signed to be signed using dsc 'electronic' : signed using slate
➔ 'slate' 'slate_certified' 'otp' (can be viewed for electronic signature only)
Email or mobile of the signing party
Reason to sign the document
'yyyy-mm-dd hh:mm:ss': Timestamp of Sign Request expiry in IST, if set. Default: 10 days from requested_on
(Optional) Represents the overall signature verification configuration.
Overall result of the document validation. Possible values: "FAIL" or "PASS."
Array of rule results, each representing the outcome of an individual validation rule applied to the document.
⮕ [ Array of rule results, each representing the outcome of an individual validation rule applied to the document. ]
Unique identifier of the validation rule
Result of the validation rule. Possible values: "FAIL" or "PASS."
➔ Specifies the logical operation (AND/OR) to be performed on the conditions within a rule.
Represents a collection of conditions that must be satisfied for the associated rule.
⮕ [ Represents a collection of conditions that must be satisfied for the associated rule. ]
Specifies the field to be checked in the condition.
Type of matching being performed for the field in the condition. Possible values: "EXACT" or "FUZZY."
Actual value of the field being evaluated in the condition.
Expected value for the field being evaluated in the condition.
Fuzzy score representing the similarity in case of fuzzy matching. Null if not applicable
Result of the condition evaluation. Possible values: "FAIL" or "PASS."
If include_authentication_url was true in the request object then this object is populated.
Sign features added upon document signing
⮕ [ Sign features added upon document signing ]
➔
➔
➔ Either SEEDING | USER_INPUT
Flag indicating whether seeding is required or not
Existing User Name
Number of pages in document
Array of signing parties
⮕ [ Array of signing parties ]
Name of the signing party
➔ 'requested': pending signature from user 'signed': signed by user 'expired': user did not sign prior to request expiry
➔ 'self': Requested from self 'org': Requested from an Organization and signatory not assigned 'signatory': Requested from an Organization and signatory has been assigned
➔ 'aadhaar': signed to be signed using aadhaar 'dsc': signed to be signed using dsc 'electronic' : signed using slate
➔ 'slate' 'slate_certified' 'otp' (can be viewed for electronic signature only)
Email or mobile of the signing party
Reason to sign the document
'yyyy-mm-dd hh:mm:ss': Timestamp of Sign Request expiry in IST, if set. Default: 10 days from requested_on
(Optional) Represents the overall signature verification configuration.
Overall result of the document validation. Possible values: "FAIL" or "PASS."
Array of rule results, each representing the outcome of an individual validation rule applied to the document.
⮕ [ Array of rule results, each representing the outcome of an individual validation rule applied to the document. ]
Unique identifier of the validation rule
Result of the validation rule. Possible values: "FAIL" or "PASS."
➔ Specifies the logical operation (AND/OR) to be performed on the conditions within a rule.
Represents a collection of conditions that must be satisfied for the associated rule.
⮕ [ Represents a collection of conditions that must be satisfied for the associated rule. ]
Specifies the field to be checked in the condition.
Type of matching being performed for the field in the condition. Possible values: "EXACT" or "FUZZY."
Actual value of the field being evaluated in the condition.
Expected value for the field being evaluated in the condition.
Fuzzy score representing the similarity in case of fuzzy matching. Null if not applicable
Result of the condition evaluation. Possible values: "FAIL" or "PASS."
If include_authentication_url was true in the request object then this object is populated.
Sign features added upon document signing
⮕ [ Sign features added upon document signing ]
➔
➔
➔ Either SEEDING | USER_INPUT
Flag indicating whether seeding is required or not
Existing User Name
Organization name registered with Digio account
'yyyy-mm-dd hh:mm:ss': Timestamp of Sign Request origination in IST
'yyyy-mm-dd hh:mm:ss': Timestamp of Sign Request expiry in IST, if set. Default: 10 days from requested_on
Organization email address registered with Digio account
➔ org
➔ api
true/false
Only applicable while creating sign request when generate access token value is passes as “true”
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.
'yyyy-mm-dd hh:mm:ss': Timestamp of generation
E Stamp Certificate ID consumed during document creation
E Stamp Certificate ID consumed during document creation
➔
➔
⮕ [ 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
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
➔
➔
(Optional) Represents the overall signature verification configuration
Determines whether to abort the signature attachment process if the conditions are not met for the associated signer. If false, it will continue to attach the signature.
➔ Specifies the maximum number of attempts allowed for the signature verification process for the associated signer.
Represents a collection of rules for the signature verification process.
⮕ [ Represents a collection of rules for the signature verification process. ]
➔ Specifies the logical operation (AND/OR) to be performed on the conditions within a rule
Represents a collection of conditions that must be satisfied for the associated rule.
⮕ [ Represents a collection of conditions that must be satisfied for the associated rule. ]
➔ Specifies the field to be checked in the condition.
➔ Specifies the type of matching to be performed on the field (e.g., exact, fuzzy).
Specifies the value to be compared against the field in the condition.
(Optional) Specifies the threshold value for fuzzy matching.
Specifies the value to be compared against the field in the condition
Fuzzy score representing the similarity in case of fuzzy matching. Null if not applicable
multi property rule
multi property rule
(Optional) Represents the overall signature conditional configuration
➔
DateTime of request creation.
DateTime of request updation.
Only applicable while creating sign request when generate access token value is passes as “true”
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.
'yyyy-mm-dd hh:mm:ss': Timestamp of generation
Contains Plugin Details like :- plugin_id , plugin_name , status
⮕ [ Contains Plugin Details like :- plugin_id , plugin_name , status ]
Contains Plugin Details like :- plugin_id , plugin_name , status
Provides Link for Authentication
Details about the exception. Usually contains the exception id for reference.
Error code
Description of the error
Custom errors
Was this page helpful?