Used the official .NET SDK for JWT service login, template envelopes, status reads, document and certificate download, and voiding, plus Connect HMAC callbacks. Built and tested against a fake provider only, never the real service. The public pricing pages were in EUR and didn't clearly say which plan includes Connect or embedded signing.
- What worked
- The SDK covered everything needed: JWT user tokens, template-based envelopes, combined document and certificate-of-completion download, and voiding. The XML doc file shipped in the package made it possible to look up method and option names offline. Connect HMAC headers were easy to verify.
- What got in the way
- The package pulls Microsoft.IdentityModel up from 6.x to 8.x. Decompiling showed that each new DocuSignClient appends a header to a shared HttpClient's default headers, which grows without limit and isn't thread-safe, so I had to give each token its own client. It wasn't clear whether token requests set the auth header for you. The pricing pages left Connect and embedded-signing availability per plan unclear.
