Sign subsequent PDFs
Follow up run of API calls up to 1 million hashes without reauthorization
Note
Reauthorization via Go>Sign Mobile application is required again after signing 1 million hashes or reaching 95 days. Early authorization can be triggered at any time by sending the Authorize credential API call.
Prerequisites
First run of the API calls executed
Access token (required for Client credential flow and Authorization code flow authentication methods)
For further signing of hashes without reauthorization, follow these steps:
To register a document:
Select 3 - PDF Service: Register Document.
To create a hash:
Attach document.
Select 4 - PDF Service: Create Hash > Send.
To extend transaction:
Select 6 - DTM: extendTransaction > Send.
To sign the hash:
Select 7 - DTM: CSC Signatures SignHash > Send.
You will receive a valid signature in the body to embed in the document.
To sign a new hash:
Select 8 - PDF Service: Embed Signature.
The SAD created in Authorize credential step will be updated automatically.
Select Send.
You will receive your document with the embedded signature.
Repeat these steps to sign additional hashes. You are required to execute Authorize credential API call after you sign 1 million hashes or reach 95 days.
To download the PDF and check the validity of the signature:
Select Save as example (bottom right) > Save response to file.
Open the PDF in Adobe Acrobat Reader to check the validity of the signature.
Note
PDFs created via the DigiCert ONE demo environment will display an invalid signature, as the certificate used is a demo and untrusted certificate. However, you can classify the root certificate as trusted in Adobe Acrobat Reader to display a green tick.