> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iinkedsign.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Qualified Electronic Signatures (QES)

> Learn how to create a signing package with Qualified Electronic Signatures (QES).

## Overview

A Qualified Electronic Signature (QES) uses a qualified digital certificate issued by a Trusted Service Provider. Enable QES when adding a package by configuring `options.digitalSignatures.signatureTypes`.

<Warning>
  Digital signatures and the selected QES provider must be enabled for your
  subscription and organization before you can use them in a signing package.
</Warning>

## Providers

The following QES providers are supported:

| Value         | Provider    |
| :------------ | :---------- |
| `digidentity` | Digidentity |

Use the serialized provider values shown in the table when configuring the request.

## Add a package with QES

Set `options.digitalSignatures.signatureTypes.qes` to an ordered array of enabled providers. QES also requires signing consent, `cac` set to `none`, and `formFlattening` set to `none` or omitted.

<Warning>
  QES is currently supported only for packages using the `Sequential` signing
  workflow.
</Warning>

<Tip>
  The final signature completed by each signer on a document is automatically
  converted to a digital signature.
</Tip>

```http Request highlight={7-17} theme={null}
POST /packages/add
{
  "name": "New Package with QES",
  "type": "Sequential",
  "state": "open",
  "options": {
    "cac": "none",
    "formFlattening": "none",
    "consentOptions": {
      "required": true,
      "requiredSigning": true
    },
    "digitalSignatures": {
      "signatureTypes": {
        "qes": ["digidentity"]
      }
    }
  },
  "signers": [
    {
      "firstName": "Signer",
      "lastName": "One",
      "email": "signer.one@example.com"
    }
  ],
  "documents": [
    {
      "fileName": "document.pdf",
      "fileId": "682f1158-e3f5-4329-8f88-c52cb5447d8c"
    }
  ]
}
```

See the [Packages add API](/v4/api/packages/add) and [digital signature options reference](/v4/reference/package-options/digital-signature-options) for the complete request contract.

## Signer experience

After the signer completes all documents in the package, they are prompted to authorize the QES through the selected provider. QES authorization is the final step in the signing session.

## Check signing status

Call `/packages/{packageId}/status` to monitor the package. A revision's `isSigned` property becomes `true` after that signer completes the revision. The document and package `isExecuted` properties become `true` after all required signers complete the signing workflow.

```http Request theme={null}
GET /packages/{packageId}/status
```

```json Response highlight={3,7,12} theme={null}
{
  "packageId": "08aba360-4466-4463-8b4b-9585d3de4b33",
  "isExecuted": true,
  "documents": [
    {
      "documentId": "d3386e4e-d5db-41f0-82ad-d3427fe57495",
      "isExecuted": true,
      "revisions": [
        {
          "revisionId": "6fcf36b4-ce54-45b9-8892-ce2d92a7e669",
          "signerId": "dff8f8cc-fe2d-428e-9a8c-bcf1a2b187ce",
          "isSigned": true
        }
      ]
    }
  ]
}
```

See the [Packages status API](/v4/api/packages/status) for the complete response.

## View the QES result

After the document is executed, download its executed PDF. The PDF contains the applied QES and certificate information for validation in a compatible PDF viewer.

```http Request theme={null}
GET /packages/{packageId}/documents/{documentId}/pdf/executed/download
```

See the [Packages download API](/v4/api/packages/download) for more information.