---
title: "Add responder to alert"
method: POST
path: "/api/{cloudId}/v1/alerts/{id}/responders"
tags: ["Alerts"]
---

# Add responder to alert

`POST /api/{cloudId}/v1/alerts/{id}/responders`

This endpoint is used to assign a responder to an existing alert. The responder is the individual or team responsible for addressing the alert. This operation streamlines the alert management process by ensuring that alerts are directed to the correct parties for timely resolution.

## Path parameters

- `id` string, required

## Request body

- AddResponderRequest
  - `id` string, required — Identifier of the responder.
  - `type` 'team' | 'user' | 'escalation' | 'schedule', required — Type of the responder.

## Response `202`

Returned if the request is successful.

- SuccessResponse
  - `result` string — Indicates the outcome of the request.
  - `requestId` string — Identifier of the request. This ID can be used to trace or track the request in the system logs or for debugging purposes in case the request fails or causes an error.
  - `took` integer

## Other responses

- `401` — Returned if the authentication credentials are incorrect.
- `422` — Returned if the payload cannot be validated.

---

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