---
title: "Update log entry channel information."
method: PUT
path: "/log_entries/{id}/channel"
tags: ["Log Entries"]
---

# Update log entry channel information.

`PUT /log_entries/{id}/channel`

Update an existing incident log entry channel.

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#log-entries)

Scoped OAuth requires: `incidents.write`

## Path parameters

- `id` string, required

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required
- `From` string, email, required

## Request body

- object
  - `channel` object, required — The parameters to update.
    - `details` string, required — New channel details
    - `type` 'web_trigger' | 'mobile', required — Channel type. Cannot be changed and must match the present value.

## Response `202`

The channel information modification was accepted.

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `429` — Too many requests have been made, the rate limit has been reached.

---

[API](https://skmtc.net/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.net/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagerduty/rest-api/versions/b679a8f3f02c/schema)