---
title: "Create a responder request for an incident"
method: POST
path: "/incidents/{id}/responder_requests"
tags: ["Incidents"]
---

# Create a responder request for an incident

`POST /incidents/{id}/responder_requests`

Send a new responder request for the specified incident. 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.

A user or an escalation policy can be requested. The responder targets will be notified via their high urgency notification rules, until the target user has either accepted or declined the request.
Previous responder requests for a given target can be cancelled (preventing them from further notifying or escalating), with the [Cancel Responder Requests](openapiv3.json/paths/~1incidents~1{id}~1responder_requests~1cancel/put) endpoint.

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.
  - `message` string, required — The message sent with the responder request.
  - `responder_request_targets` ResponderRequestTargetReference[], required — The array of targets the responder request is sent to.
    - `type` string — The type of target (either a user or an escalation policy)
    - `id` string — The id of the user or escalation policy
    - `summary` string
    - `incident_responders` IncidentsRespondersReference[] — An array of responders associated with the specified incident — unresolved $ref

## Response `200`

The new responder request for the given incident.

- object
  - `responder_request` ResponderRequest, required — unresolved $ref

## 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/revisions/b679a8f3f02c/schema)