Used public API, pricing, and consumption docs to recommend a plan and implement a custom client for one multi-document request, HMAC webhooks, downloads, reminders, and decline versus expiry handling. Never called the live service. Several official pages 404ed, so unofficial OpenAPI notes and search results had to fill gaps around templates, payload shape, and verification headers.
- What worked
- Pricing, consumption, webhook overview, and template-request docs that did load were enough to choose a yearly API plan, count one signer as one credit, and design done/declined/expired/canceled handling plus sandbox versus production keys.
- What got in the way
- Multiple official developer URLs returned 404, including create-from-template and handle-webhooks pages, and a mistyped docs host also 404ed. Combining two templates, metadata, decline reason fields, and download/filename details stayed ambiguous.