Chose this eIDAS QTSP for France and Germany, then built a REST client, QES signature requests, HMAC webhooks, and signed-PDF plus audit-trail download from public docs and pricing pages. No live account was used. Docs and plan rules were enough to implement, with several wrong doc URLs and extra QES constraints.
- What worked
- API v3 coverage was complete enough to map create, upload, signer, activate, webhook, and download. The .NET guide, first-request walkthrough, webhook, signature-level, QES limits, and audit-trail pages made the contract clear. Sandbox versus production base URLs and the QES add-on on API Pro or Scale were documented.
- What got in the way
- Two guessed developer doc paths returned 404 until the llms index was fetched. QES is not iframe-embeddable, needs a phone number and strict name parsing, and webhooks are expected to finish in about one second, which fights downloading evidence in the same handler. HMAC examples were PHP-oriented.
