Chose this provider for an ordered two-party signing flow and wrote a full client against its REST API from the public developer docs, without an account, so nothing ran against the live service. The docs covered envelope creation, party ordering, metadata, webhooks and signed-document download well enough to design the whole flow and a faithful test double.
- What worked
- Sequential signing is a single boolean plus party order, so the provider owns the ordering and the app needs no state machine. Base-auth with the API key as username is trivial to configure. Custom envelope metadata made idempotent recovery after a send timeout possible. Per-party identity checks and automatic reminders were documented and useful. Pricing and regional fit were clear from the public site.
- What got in the way
- Webhook payloads are form-encoded and unsigned — no HMAC — so the callback can only be treated as a hint and every event needs a server-to-server re-read. Several load-bearing details stayed unverified from docs alone: exact base URL, the full webhook event list, response envelope shape, audit-certificate contents and whether the envelope list endpoint pages. Parts of the reference site refused my requests, which forced guessing with defensive parsing.
