2. Initiate Signing Process
The obtained signing identity and txId during the previous step needs to be passed in the next API call along with the single or multiple documents to be signed.
PUT http://localhost:8080/v2/signature/request
Headers
Content-Type
multipart/form-data
Body
digestAlgorithm
SHA256
signIdentityId
ckqtokgre4o5mrk4bajtk413ui
txId
90ca005cfb4d4827b1247889166b72fe
file
file1.pdf file2.pdf
sigProp
{ "signPropDetail": [ { "fileName": "file1.pdf", "signInfo": "1:50, 50, 200,200]" }, { "fileName": "file2.pdf", "signInfo": "1:[50,50,200,200]" } ] }
Response
Provide the below values for “signProp” parameter in the API call. The values should be adjusted accordingly as per the files.
Description of parameters in the above request body:
filename
The name of the file that needs to be signed. It should be exactly same as the selected one.
signInfo
Page number and the signing position on the specified page. The first 2 values (50,600) specify the values for lower left corner X,Y coordinates and other two 200,100) represent the upper right corner X,Y coordinates.
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
signProp
As described above
Sample Curl Command
Last updated
Was this helpful?