2. Initiate Signing Process
Last updated
Last updated
Invoke the above URL (as shown in the screenshot) in browser to obtain the sign identities and transaction id value. The transaction id remains valid for 10 mins.
The above obtained signing identity and txId needs to be passed in the next API call along with the document.
PUT
http://localhost:8089/v2/signature/request
Name | Type | Description |
---|---|---|
Content-Type | string | multipart/form-data; |
List of attributes for request body:
Attributes | Description |
---|---|
txId(mandatory) | Transaction id for signing request Note: Transaction ID is valid for only 10 minutes and operation should end within the same period. |
digestAlgorithm(mandatory) | Entity can use one of the digest algorithms from below according to their requirement: SHA256 SHA384 SHA512 |
signIdentityId(mandatory) | User’s qualified certificate id |
file(mandatory) | Pdf file which is to be signed |
sigRect(optional) | Default values: [36,748,108,32] First two values are X and Y co-ordinates, second two values are width and height of the signature dimensions. |
sigPageNo(optional) | Default page: 1 Page number where signature is to be appeared Example: 1 |
SPCustomerIdRef (mandatory) – passed as query parameters. | The value of this header should represent unique extended customer identification. If Service provider is consuming hash signing API’s for their own organization then this value should be passed as “self”. If Service provider is consuming hash signing API’s for other organizations or for selling the application then this value should be passed as “Organization name”. Example: Organization name is : Dubai Health Authority : Value should be passed as “DHA” |