Skip to main content
Document Signing

Read document signing extension

GET/v4/config/platform/extension/document-signing

Reads the configuration of the Document Signing extension. With it, a person signs a PDF document from the EUDI Wallet with a qualified electronic signature, using a Qualified Electronic Signature Access Credential (QESAC).

Upload the documents with POST /v4/config/ows/verifier/document-signing-files, then send a verification request with presentationDefinitionId and the file as transaction data (OpenID4VC API, verifier).

The answer is 404 when the extension is not enabled, also while it waits for its signing key (awaitingKey). Turn it on first with PUT /v4/config/platform/extension/documentSigning and a signingKeyId.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:extensions:read

Response

application/json

The configuration of the extension.

  • extensionStatusboolean

    Always true in this answer. An extension that is not enabled gives 404.

  • presentationDefinitionIdstring<uuid>

    The system-managed presentation definition of the extension. It asks for the QESAC.

  • labelstring

    The label of the presentation definition.

  • qualifiedElectronicSignatureProviderstring

    The qualified trust service provider that makes the signature.

  • documentStorageProviderstring

    Where the service keeps the uploaded and the signed documents.