---
title: "Cancel responder requests for an incident"
method: PUT
path: "/incidents/{id}/responder_requests/cancel"
tags: ["Incidents"]
---

# Cancel responder requests for an incident

`PUT /incidents/{id}/responder_requests/cancel`

Cancel pending responder requests for the specified incident.

This endpoint allows you to cancel responder requests for specified targets that are in a pending state. Only responders who have not yet joined or declined can be cancelled. This endpoint requires the account to have access to the [responder requests](https://support.pagerduty.com/main/docs/add-responders) feature.

**Account Ability Requirement**: The account must have the `coordinated_responding` ability. Returns 402 Payment Required if the ability is missing. You can use the [List Abilities API](openapiv3.json/paths/~1abilities/get) to check account abilities.

**State Constraints**: Only responders in the `pending` state can be cancelled. Responders who have already `joined` or `declined` are not affected (the result will indicate their current state).

**User vs Escalation Policy Behavior**:
- **Users**: Direct cancellation, updates state to `user_cancelled`, stops notifications
- **Escalation Policies**: Stops the escalation process, updates state of all pending users from that escalation policy to `user_cancelled` and stops notifications

**Result Values**:
- `cancelled`: Successfully cancelled
- `joined`: User already joined (not cancelled)
- `declined`: User already declined (not cancelled)
- `not_found`: Target not found or not part of any responder request

Scoped OAuth requires: `incidents.write`

## Path parameters

- `id` string, required

## Headers

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

## Request body

- object
  - `requester_id` string, required — The user id of the requester.
  - `responder_request_targets` object[], required — The array of targets to cancel.
    - `type` 'user_reference' | 'escalation_policy_reference', required — The type of target (either a user or an escalation policy)
    - `id` string, required — The id of the user or escalation policy

## Response `200`

The result of cancelling responder requests for the given incident.

- object
  - `responder_request_targets` object[], required — The array of targets with their cancellation results.
    - `type` 'user_reference' | 'escalation_policy_reference', required — The type of target (either a user or an escalation policy)
    - `id` string, required — The id of the user or escalation policy
    - `result` 'cancelled' | 'joined' | 'declined' | 'not_found', required — The result of the cancellation attempt

## 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.
- `402` — Account does not have the abilities to perform the action. Please review the response for the required abilities. You can also use the [Abilities API](#resource_Abilities) to determine what features are available to your account.
- `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)