Direct e-Sealing CAdES Request Body

The request body below shows a CAdES example. Use the signature_form and signature_profile values enabled for your client.

{
  "client_id": "client-id",
  "files": [
    {
      "fileName": "document.pdf",
      "fileContent": "rxr4oMRqMAjrAdhgXjjYeLlh285M9UU1wxj+ksg3efY=",
      "mimeType": "application/pdf"
    }
  ],
  "signature_form": "CAdES",
  "signature_profile": "CAdES_BASELINE_T"
}

Property	Type	Description
client_id	string	Required. Your eID Easy API client ID.
files	array	Required. File digests to e-seal.
files[].fileName	string	Required. File name of the original file.
files[].fileContent	string	Required. Base64-encoded SHA-256 digest of the original file.
files[].mimeType	string	Required. MIME type of the original file.
signature_form	string	Required. Signature form to produce.
signature_profile	string	Required. Signature profile to produce.

Request constraints:

• files must contain at least 1 file and at most 30 files.
• files[].fileName must be at least 3 characters long.
• Each files[].fileName must be unique within the request.
• files[].fileContent must be the base64-encoded SHA-256 digest of the original file.
• files[].mimeType must be a valid MIME type.

Direct e-Sealing CAdES Response Example

If the request succeeds, the API returns one signature for each input file digest. For example, a CAdES response looks like this:

{
  "status": "OK",
  "signatures": [
    {
      "fileName": "document.pdf.p7s",
      "mimeType": "application/pkcs7-signature",
      "fileContent": "base64-encoded-signature"
    }
  ]
}

Property	Type	Description
status	string	OK when the request succeeded.
signatures	array	Signatures for the submitted file digests.
signatures[].fileName	string	Signature file name. For CAdES, the file name usually ends with .p7s.
signatures[].mimeType	string	Signature MIME type, e.g. application/pkcs7-signature.
signatures[].fileContent	string	Base64-encoded signature content.