Just like emails, letters can also be connected in Enneo in two ways, depending on the requirements: IMAP and API.

​
Import of letters as emails via IMAP

This solution is recommended when a scanning service is used that converts incoming letters into emails with the letters as an attachment (e.g. PDF). The following steps are necessary to connect letters:
  1. Connect the mailbox as described here: Connect Emails
  2. Ensure that the emails are recognized as letters. Enneo recognizes an email as a letter if the following criteria are met:
    • The sender of the email is the scanning service. The sender’s email address can be specified in the letter settings.
    • The subject of the email contains only the word “LETTER”. If another keyword is preferred, this can be adjusted in the letter settings.

​
Import of letters via REST API

  1. When importing letters via the API, the channel attribute must be set to “letter”. Enneo takes care of the rest.
  2. An example of a request with minimal parameters: 
curl --location 'https://demo.enneo.ai/api/mind/ticket' \
--header 'Authorization: bearer <token>' \
--data '{
    "channel": "letter",
    "process": "batch",
    "attachments": [
        {
            "base64": "base-64-encoded-string-of-pdf-or-image-file",
        }
    ]
}
Notes:
  • The process parameter can either be set to batch (standard) or realtime. In realtime, the letter is processed immediately and not asynchronously by the AI, which can make the request a bit longer.
  • Attachments can either be uploaded as Base64-encoded files via the base64 parameter or provided via a URL with the url parameter.
  • All ticket attributes defined in the API specification can also be specified. This is useful for transmitting metadata such as a contract ID, tags, or a creation date.

​
Supported file formats

Enneo supports automatic conversion of attachments in the following formats:
  • PDF
  • PNG
  • JPG
  • TIFF