Generating documents and capturing esignatures in your apps using Adobe Sign
summary
Shows how to produce a PDF from a Word template, upload it as a transientDocumentId, create an agreement via the Adobe Sign REST API, and return an embeddable signing URL that actually opens and can be signed. Covers auth options (OAuth vs integration key), field tagging approaches (text tags, library templates, Document Generation Tagger), identity verification options (email, SMS, government ID, KBA, qualified signatures), and using webhooks to retrieve completed documents — demo completes successfully.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 5:00Validate identity
- 5:47Identity verification methods
- 8:50Adobe Sign integrations
- 9:50Document types
- 12:45Document Generation Tagger
- 14:15Adobe Sign vs PDF Services
- 15:00Getting started with Adobe Sign
- 16:20API Reference
- 17:05Getting Started
- 18:45OAuth Access Token
- 19:30Base URL
- 20:20Sending an agreement
- 24:35Testing the agreement
- 25:35Signing the document
- 27:35Webhooks
- 28:40Resources
related talks
20mQualified cloud signatures with Adobe Sign
45mAutomate and protect your documents with Adobe and Microsoft 365
21mCan an advanced e-signature be an alternative to the qualified e-signature?
21mHow the digital signature streamlines processes in an auditing firm
23mElectronic Signature in HR – How to Make It Finally (Even) Easier
47mElectronic Signatures from the Perspective of Java Developers
14mQualified electronic signature
15mDemystifying Digital Signatures