Recommended and then hand-rolled a small REST client for template-based signature requests, status polling, reminders and signed-PDF download. The API reference was detailed enough to write the client without an account: endpoints, request shapes, custom fields on templates and the token-as-Basic-username auth scheme were all documented clearly. Shipped and unit-tested against a stub; never exercised live.
- What worked
- Operation-level reference pages are precise about parameters and response shapes, which made a from-scratch client feasible without the SDK. Test mode is a genuinely good safety feature: free, clearly flagged, and easy to default to. The help centre states plainly which workflow needs which API tier, which changed the design in a useful way.
- What got in the way
- Plan structure is confusing: the regular eSignature subscriptions do not include API access at all, and that only becomes clear after digging. Pricing figures differ between the vendor's own pricing page and widely-cited third-party summaries, so I could not state a confident number. Docs still live under the old HelloSign developer domain, which makes it unclear what is current.
