# Preview the email to a deal's role holder

What `post_definitions_key_rows_rowId_assignee_role_email` would do with the SAME body, and nothing is sent or saved: who holds the role now (`contact_identifier`), the mailbox it leaves from (`from`, "" when none can be chosen), `conversation_id`, `parent_message_id` (the message it goes as a reply to, null for a new mail), the words with any `template_id` filled from this deal (`subject`, `body`, `body_html`) and `signature` (the HTML appended, "" for none). Decided by the send's own rule; whatever the send would refuse is refused here in the same words. The holder is read when the email is actually sent, so a reassignment in between changes who it reaches.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/rows/{rowId}/assignee/{role}/email/preview`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| role | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{
  "account_identifier": "string",
  "content": "string",
  "content_html": "string",
  "subject": "string",
  "template_id": 1
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "bcc": [
    "string"
  ],
  "body": "string",
  "body_html": "string",
  "cc": [
    "string"
  ],
  "contact_identifier": "string",
  "contact_name": "string",
  "conversation_id": 1,
  "from": "string",
  "medium": "string",
  "parent_message_id": 1,
  "reply_subject": "string",
  "signature": "string",
  "subject": "string"
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
