Zum Hauptinhalt springen
POST
/
contract
/
legitimation
/
preview
Dry-run customer legitimation check
curl --request POST \
  --url https://demo.enneo.ai/api/mind/contract/legitimation/preview \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data @- <<EOF
{
  "channel": "email",
  "contractId": "715559",
  "customerId": "C-987",
  "from": "kunde@example.com",
  "subject": "Question about my contract",
  "bodyPlain": "My contract number is 715559 and I'd like to change my address.",
  "rawData": {},
  "subchannelId": "3"
}
EOF
{
  "legitimationLevel": 10,
  "legitimationMessage": "<b>Group 1</b>: needed 2, got 1 criteria.",
  "detectionLog": [
    "<string>"
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.enneo.ai/llms.txt

Use this file to discover all available pages before exploring further.

Autorisierungen

​
Authorization
string
header
erforderlich

JWT-based authentication

Body

application/json
​
channel
string
erforderlich

Ticket channel. Determines which rule set is used (sync: chat/phone, async: all others).

Beispiel:

"email"

​
contractId
string

Optional. If provided, the real contract is loaded from the ERP and used for criteria evaluation.

Beispiel:

"715559"

​
customerId
string

Optional override for the customer ID on the loaded contract.

Beispiel:

"C-987"

​
from
string

Sender address (email or phone number).

Beispiel:

"kunde@example.com"

​
subject
string

Ticket subject line.

Beispiel:

"Question about my contract"

​
bodyPlain
string

Plain-text ticket body.

Beispiel:

"My contract number is 715559 and I'd like to change my address."

​
rawData
object

Synthetic ticket.rawData JSON object — same shape as the raw payload Mind writes to the ticket table on incoming tickets.

​
subchannelId
string

Optional subchannel ID. If the subchannel has assistantAuthenticationInstructions, the deprecated path is used.

Beispiel:

"3"

Antwort

Legitimation check result

​
legitimationLevel
integer

0=no customer, 10=identified but not legitimized, 20=legitimized

Beispiel:

10

​
legitimationMessage
string | null

Human-readable explanation of why legitimation failed. null on level 0 and 20.

Beispiel:

"<b>Group 1</b>: needed 2, got 1 criteria."

​
detectionLog
string[]

Step-by-step evaluation log for debugging.