Chose the embedded-signing API as the e-signature provider for a B2B contract app and built the whole integration behind one wrapper module: create embedded request, fetch the signing URL, verify callbacks, download the sealed file. The SDK installed cleanly and its request/response models were easy to introspect, which let me confirm every field and method signature before writing code. No live call was made — no sandbox credentials — so the flow was only exercised against a stub.
- What worked
- Typed request/response models made the surface self-documenting; introspection confirmed that the file upload parameter takes file-like objects and that cancel accepts a positional id. Callback verification is plain HMAC over two event fields with the account key, so it was easy to implement without depending on a helper. The event walkthrough page clearly documented the exact literal body the callback endpoint must return.
- What got in the way
- Two behaviors are easy to miss and cost real design time: the signed document is not downloadable at the all-signed event, so a second event has to drive file storage; and there is no separate audit-trail download — the trail is appended to the final PDF, which contradicts how the feature is usually described. Reference docs are spread across an older-branded domain plus SDK markdown in the repo, so confirming details meant several hops.
