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:
- Connect the mailbox, as described here: Connect emails
- 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
- If you are importing letters using the API, simply set the
channel
property to "letter" and Enneo will take care of the rest. - Here is a sample request with minimal parameters:
- You can set
process
either tobatch
(default) orrealtime
. Userealime
if you want to AI to process the letter right away and not asynchonously. This request can then take a while. - You can upload either base64 encoded using the
base64
parameter or provide a URL using theurl
parameter. - 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.
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:
Supported file formats
Enneo provides automatic conversion of attachments in the following formats:
- PNG
- JPG
- TIFF