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

# Update a channel

> Update Channel binding, display name, enable state, or response options.

`POST /api/v1/forward/channels/{channel_id}`

Uses merge-patch semantics. Omitted fields remain unchanged.

## Headers

| Header            | Required | Description                                   |
| ----------------- | -------- | --------------------------------------------- |
| `Authorization`   | Yes      | `Bearer <PAT>`                                |
| `Content-Type`    | Yes      | `application/json`                            |
| `Idempotency-Key` | No       | Optional idempotency key for unsafe requests. |

## Path parameters

| Parameter    | Type   | Required | Description |
| ------------ | ------ | -------- | ----------- |
| `channel_id` | string | Yes      | Channel ID. |

## Body parameters

| Parameter                         | Type    | Required | Description                      |
| --------------------------------- | ------- | -------- | -------------------------------- |
| `name`                            | string  | No       | Channel display name.            |
| `identity_id`                     | string  | No       | New bound Forward Identity ID.   |
| `template_id`                     | string  | No       | New bound Forward Template ID.   |
| `enabled`                         | boolean | No       | Manual enable or disable switch. |
| `channel_config.response_options` | object  | No       | Reply visibility settings.       |

## Example request

```bash theme={null}
curl -s -X POST 'https://api.qoder.com/api/v1/forward/channels/channel_019eabc123' \
  -H "Authorization: Bearer $QODER_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": false,
    "channel_config": {
      "response_options": {
        "include_tool_calls": true,
        "include_thinking": false
      }
    }
  }'
```

## Example response

**HTTP 200 OK**

```json theme={null}
{
  "id": "channel_019eabc123",
  "type": "channel",
  "identity_id": "idn_019eabc123",
  "template_id": "tmpl_support",
  "channel_type": "feishu",
  "name": "Support Feishu channel",
  "enabled": false,
  "binding_status": "bound",
  "channel_config": {
    "response_options": {
      "include_tool_calls": true,
      "include_thinking": false
    }
  },
  "created_at": "2026-06-18T10:00:00Z",
  "updated_at": "2026-06-18T10:30:00Z"
}
```

## Response fields

Returns the updated Channel object.

## Errors

| HTTP | Type                    | Code                         | Trigger                      |
| ---- | ----------------------- | ---------------------------- | ---------------------------- |
| 400  | `invalid_request_error` | `invalid_request`            | Request body is invalid.     |
| 404  | `not_found_error`       | `channel_not_found`          | Channel does not exist.      |
| 404  | `not_found_error`       | `channel_template_not_found` | New Template does not exist. |
| 404  | `not_found_error`       | `channel_identity_not_found` | New Identity does not exist. |
| 409  | `conflict_error`        | `channel_identity_disabled`  | New Identity is disabled.    |

## Notes

* `id`, `type`, and `channel_type` cannot be updated.
* `binding_status` is system-maintained.
* `enabled=true` only opens the manual switch. It does not change `binding_status`.
* Updating `identity_id` or `template_id` may stop reusing existing conversation bindings; new inbound messages use the new binding.

## Related

<CardGroup cols={2}>
  <Card title="Get a channel" icon="file-lines" href="/cloud-agents/api/forward/channels/get" />

  <Card title="List channels" icon="list" href="/cloud-agents/api/forward/channels/list" />
</CardGroup>