Installed the official Python SDK at 1.13.0 and used it to shape embedded signature requests, short-lived sign URLs, webhook checks, and zip downloads of the signed document and audit trail. Imports and model inspection worked, but upload shapes, callback parsing, and status-code meaning only became clear after reading the generated client and a help article. No live account or signing ceremony was called.
- What worked
- The SDK exposes embedded request creation, a sign URL for a signer id, and a zip download that can hold the completed PDF and a separate audit trail. The package installed and imported on the first attempt, and a version-pinned embedded browser script (2.12.0) answered a header check on the public CDN.
- What got in the way
- Generated hints describe a three-part file tuple while the serializer unpacks two, and a byte stream is a poor upload because it has no filename. A 409 on the sign URL means the request is already signed, which is easy to treat as a not-ready download. Callback helper classes were awkward enough that payloads were parsed and verified manually. Sign URLs expire quickly and on first open, and a separate audit PDF depends on an account setting. The live API and iframe were never opened.
