Dry-run customer legitimation check

`POST /contract/legitimation/preview`

Evaluates the configured legitimation rules (customerLegitimationRuleAsyncChannels / customerLegitimationRuleSyncChannels) against a synthetic ticket built from the supplied fields. No data is written. Useful for testing legitimation settings without a real ticket.

Request body

channelstringbodyrequired

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

contractIdstringbody

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

customerIdstringbody

Optional override for the customer ID on the loaded contract.

fromstringbody

Sender address (email or phone number).

subjectstringbody

Ticket subject line.

bodyPlainstringbody

Plain-text ticket body.

rawDataobjectbody

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

subchannelIdstringbody

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

Request Example

{
  "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": null,
  "subchannelId": "3"
}

Responses

200 — Legitimation check result

Response Example

{
  "legitimationLevel": 10,
  "legitimationMessage": "<b>Group 1</b>: needed 2, got 1 criteria.",
  "detectionLog": [
    "string"
  ]
}

400 — Missing required field

403 — Unauthorized

404 — Contract not found