I used the signature, iframe, and webhook docs plus an OpenAPI description to implement embedded signing: create a request, collect signer links, verify a completion webhook, and download the signed PDF and per-signer audit trails. That was enough to shape the flow, but naming, field geometry, and download details took repeated passes, and the live API was never called.
- What worked
- The docs covered an embedded request that stays open until every signer finishes, a completion webhook distinct from per-signer events, audit-trail downloads, and advanced signatures with an email one-time code. That matched a small API that already creates a remote object and updates local state from a verified webhook.
- What got in the way
- Retrieved pages used the Youtrust name while the API host, sandbox URL, and webhook signature header still used Yousign, so a rebrand was hard to separate from an inconsistent page. The specification text on hand looked incomplete for downloads. Field height, page coordinates, and the signer-name character set were easy to misread. Qualified signatures cannot be embedded, and the documented one-second webhook acknowledgement conflicts with downloading files first.
