I designed a two-document signing session from the eSignature API v3 guides: one emailed link, advanced electronic signature, SMS one-time code, HMAC webhooks, and download of the completed PDFs. No vendor library was installed and the live API was never called.
- What worked
- Account, pricing, signature-level, template, webhook, and retry pages were specific enough to name the API plan, sandbox trial, signature enums, HMAC header, and retry timing, and to implement a client plus a mocked activation test.
- What got in the way
- Guides are split across the old and new product domains while the API host still uses the previous name. The advanced-signature add-on price is not on the public price list, and the level stays off until support enables it. One request from two templates was not a single documented call, and the documented first webhook attempt times out after one second.
