# Resolve a thread

Settles a thread, or with `{resolved: false}` reopens it — one route for both directions so the word and the stamp cannot disagree. Resolving is a STAMP, not a wall: the thread keeps its transcript, keeps answering reads and keeps taking messages, and a new message reopens it. What it stops is the list counting the thread as live work.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/threads/{threadId}/resolve`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| threadId | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "resolved": true
  },
  "params": {
    ":key": "string",
    ":threadId": ""
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "createdAt": "string",
    "createdBy": 1.5,
    "definitionKey": "string",
    "id": "",
    "lastMessageAt": "string",
    "messageCount": 1.5,
    "participants": [
      {
        "addedAt": "string",
        "email": "string",
        "isMuted": true,
        "lastReadAt": "string",
        "name": "string",
        "role": "string",
        "userId": 1.5
      }
    ],
    "recordName": "string",
    "resolvedAt": "string",
    "resolvedBy": 1.5,
    "rowId": "",
    "status": "string",
    "subject": "string",
    "unread": 1.5,
    "updatedAt": "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"
}
```