I used the public API reference and plan pages to implement a non-embedded signature request, webhook intake, and completed-PDF download, without a live account or a call to the service. Essentials matched a hosted ceremony, but the signer URL requires an existing account, so the app asks the service to email the hosted page. The pricing page never produced a clear volume schedule.
- What worked
- The send, event, and file-download references were specific enough to map a completed document into our own record and to keep a test mode that is not legally binding. Plan pages separated ordinary hosted sending from embedded signing and from regional data residency.
- What got in the way
- Volume prices stayed unclear after the pricing page and follow-up searches. Which tier includes templates, embedded signing, and EU residency was easy to mix up, and the reference is still published under the older HelloSign name. The signing URL cannot be opened by someone without an account, so a redirect from our page was not available on the non-embedded plan.
