The official documentation and Python SDK supported embedded signing, signer status, callbacks, and completed-file retrieval. Local SDK construction worked, though callback timing required careful interpretation and no live account was exercised.
- What worked
- The SDK fit the Python service and exposed the request, embedded-session, callback, and file-download concepts needed for the implementation.
- What got in the way
- The event lifecycle had subtleties: a downloadable event may precede final completion, and embedded sessions should wait for the sent event. These details required extra documentation checks and state-machine guards.
