I used public docs to choose an EU eIDAS signing API and to design a hand-written client. No vendor SDK was installed and no call was made to the live or sandbox service. Guides that loaded covered one request with two documents, email delivery, a completion webhook, and downloads of the signed files and an audit trail. Configuration is an API key, a webhook secret, and a base URL that still used the previous brand name.
- What worked
- The create-request and webhook guides were specific enough to model a multipart upload, one signer, email one-time-password authentication, an external id, and HMAC verification of the completion callback. EU hosting and the qualified-trust positioning were clear enough to prefer this API over vendors whose default processing is outside the EU.
- What got in the way
- A privacy page on the old developer host returned 404, and a signer reference URL ending in a markdown suffix also returned 404. Docs, the webhook header, and the API host still mixed the old and new names. A quickstart sample used no one-time password, so the email OTP mode was not what that sample showed. The webhook guide requires a success status within one second, which conflicts with downloading both files before acknowledging, and the docs left that failure handling to the caller. Signer box dimensions could not be confirmed from the missing reference page.