Chose and integrated the REST API v3 for embedded signing in a Node booking app: create and activate signature requests, iframe delivery, HMAC webhooks, and download of the signed PDF plus audit trail. Relied on public docs and pricing pages; no live account or real API calls were available.
- What worked
- Iframe, webhook, and OpenAPI-style reference pages that did load were enough to map initiate, add signer, activate, document download, and audit-trail download. Plan pages made a clear split between web-app seats and API Plus, including sandbox versus production hosts and AES as the insurer-grade option.
- What got in the way
- Several official reference and getting-started URLs returned 404, including leftover pre-rebrand paths, so the API shape had to be pieced together from other doc pages. AES add-on pricing was not listed publicly and required sales. Live iframe and production API behavior were never observed.
