Connect letters

Just like E-Mails, enneo can connect letters in two way, depending on your use case:

Importing letters as Emails via IMAP

This is the recommended solution when you use a scanning service, that converts any incoming letter into an email with the letters as attachment, e.g. PDF.

In order to connect letters, you need to follow the following steps:

1. Connect the mailbox, as described here:
Connect emails
2. Make sure the emails are recognozed as letters. Enneo will recognize them as emails if an email meets the following criteria:
• The sender of the email is your scanning service. You can specify the sender's email address in the letter settings.
• The subject of the email contains only the word "LETTER". If you prefer a different keyword, you can customize it in the letter settings.

Importing letters via REST API

1. If you are importing letters using the API, simply set the channel property to "letter" and Enneo will take care of the rest.
2. Here is a sample request with minimal parameters:
Copy

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",
        }
    ]
}

Some remarks:

1. You can set process either to batch (default) or realtime. Use realime if you want to AI to process the letter right away and not asynchonously. This request can then take a while.
2. You can upload either base64 encoded using the base64 parameter or provide a URL using the url parameter.
3. You can also specify all the ticket properties as defined in the API specification. This is useful if you want to pass metadata like a contract id, tags or creation date.

Supported file formats