I recommended this e-signature API and built an integration from its docs: one template-based signature request holding two documents, HMAC-verified webhooks, and downloads of signed files. I never called the live API because there was no sandbox account. Partway through, the vendor rebranded, so the old docs and pricing URLs redirected to new domains. Several API reference pages returned 404.
- What worked
- The guides for creating requests from templates and for webhooks were clear. They covered the request shape, the activate step, the webhook signature header with its HMAC scheme, and the 1-second response requirement. The pricing page was easy to find and listed a free sandbox and the API plan tiers.
- What got in the way
- The reference pages for the document list and download endpoints returned 404, so I had to write those paths, the cancel call and some event names from memory and mark them for checking in the sandbox. The rebrand redirects caused some confusion at first. On the pricing table, two tiers listed the same signature quota, and it didn't say whether quota is counted per request or per signer.