The API Usage section lists simple tasks that can be performed using the Sign APIs. However, you can also use the APIs in other simple to complex signing scenarios as mentioned in this guide.
A common scenario involves an application where users need to sign documents within the application as part of a process. For example, a partner portal for onboarding new partners that requires them to sign an NDA or an e-commerce application that requires users to sign a purchase agreement. In these cases, the document is not sent to recipients for signature, but is presented to them within your application.
For this type of integration, Acrobat Sign supports creating a Widget through the Acrobat Sign APIs. A widget is like a reusable template that can be presented to users multiple times and signed multiple times. Each time a widget gets signed, the signed document becomes a separate instance of the document. A good way to think about the relationship of the widget and the documents signed through it is a parent-child relationship. A widget can be presented either to an anonymous signer, in which case Acrobat Sign can validate the signer’s identity as part of the signing process, or to a signer whose identity can be specified through the API by the hosting application.
Now, consider a scenario where parents’ consent is required for young school-going kids to do some light work as part of their school trip. In this case, the school is required to get the parent’s consent by asking them to sign a form. Once the form has been completed and signed by the child’s parent, the school can engage the kid with the planned activities.
The entire consent workflow can be achieved through the Sign APIs.
The school does the following:
Creates a Sign Widget with the required details and form elements.
The Widget URL is circulated to all the parents.
Whenever a parent signs the widget, a signed agreement can be downloaded by the school.
You can create a signable web form (Widget) by uploading any standard document and adding fields using the drag-and-drop interface provided by Acrobat Sign. You can also upload an existing PDF form with its fields, or insert text tags into a document which Acrobat Sign will automatically turn into form fields. You can do all of these through the Sign APIs.
Before you begin creating a Widget, learn to Send for Signing (Create an Agreement).
Creating a Widget¶
See Create a Widget
Each time a widget is signed by a parent, a separate instance of a document gets created. To get the agreements created using the widget, see Download the Agreement.
The Sign APIs can also be used for scenarios involving in-person signing. Consider an example wherein you need to get the photo publishing rights of a celebrity. You can use the in-person signing technique to simplify the signing process for the celebrity.
The steps involved are:
Upload a document the document containing the terms and conditions involving photo publishing.
Create an agreement and Get the Signing URL for the agreement. Load the signing URL in a mobile device and get it signed from the celebrity, in-person.
Once the celebrity signs, Download the Agreement.