> ## Documentation Index
> Fetch the complete documentation index at: https://dev.docs.1to1ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change conversation state

> Marks the conversation as resolved or pending

<Info>
  **Endpoint** · `POST /conversation/actions`
</Info>

Two actions change the conversation's state (`inbox_status`): `mark_resolved`
marks it as **resolved** and `mark_pending` as **pending**. Neither carries
fields.

## `mark_resolved`

Marks the conversation as resolved.

```jsonc theme={null}
{
  "type": "mark_resolved"
}
```

<Note>
  If the thread has untranscribed audio, `mark_resolved` can fail with
  `TRANSCRIPTION_REQUIRED_TO_RESOLVE` (integrity guard). It does not escalate to a
  human: fix it and retry.
</Note>

## `mark_pending`

Marks the conversation as pending.

```jsonc theme={null}
{
  "type": "mark_pending"
}
```

In a list, these objects go in the `actions` array of a `POST /conversation/actions` — see [Assembling an action list](/en/action-groups/overview#assembling-an-action-list).

## Executable example

The `mark_resolved` and `mark_pending` actions on a conversation identified by
phone and channel. Neither carries fields: they only change the `inbox_status`.

### Request

<CodeGroup>
  ```bash Mark as resolved theme={null}
  curl -X POST "https://app.1to1.ai/api/v1/public/{slug}/conversation/actions" \
    -H "Authorization: Bearer sk_1to1_your_api_key" \
    -H "Content-Type: application/json" \
    -d '{
      "conversation": {
        "phone": "+5215512345678",
        "channel": "ch_7A9K2M4Q"
      },
      "actions": [
        {
          "type": "mark_resolved"
        }
      ]
    }'
  ```

  ```bash Mark as pending theme={null}
  curl -X POST "https://app.1to1.ai/api/v1/public/{slug}/conversation/actions" \
    -H "Authorization: Bearer sk_1to1_your_api_key" \
    -H "Content-Type: application/json" \
    -d '{
      "conversation": {
        "phone": "+5215512345678",
        "channel": "ch_7A9K2M4Q"
      },
      "actions": [
        {
          "type": "mark_pending"
        }
      ]
    }'
  ```
</CodeGroup>

### Response

`202 Accepted` — the group was accepted and runs in the **background**. The
per-action result does not travel in the response (query it later — see [How it runs](/en/action-groups/overview#how-it-runs)).

```json theme={null}
{
  "status": "processing",
  "actions_accepted": 1
}
```

<ResponseField name="status" type="string">
  Always `processing`: confirms the group was accepted and is running.
</ResponseField>

<ResponseField name="actions_accepted" type="integer">
  How many actions in the array were **admitted** for execution — not how many
  succeeded.
</ResponseField>