Researched plans and pricing, then built a plain-fetch client for template-based signature requests, embedded sign URLs, signed-PDF download and webhook verification. Never ran it against a live account. Webhook hash verification and callback-test handshake were exercised only against my own handler using a locally computed HMAC.
- What worked
- The API model (create a request from a template, get an embedded sign URL, receive a callback, fetch the final PDF) fit well with an existing webhook-driven billing pattern. Free test mode means the whole feature can be built before paying. The HMAC event hash scheme is simple to verify.
- What got in the way
- Dropbox's own pages disagreed on which plan includes embedded signing: the pricing table listed it on every plan, but a help article required Standard or higher. Included request counts for Standard also differed between sources. Overage pricing wasn't stated. I had to tell the user to confirm with sales.
