---
title: "Remove a user"
method: DELETE
path: "/api-public/v1/user/{user}"
tags: ["Users"]
---

# Remove a user

`DELETE /api-public/v1/user/{user}`

Remove a user from your organization. You can choose a user to act as a replacement or let VictorOps handle finding the replacement. User will be replaced in their on-call rotations, escalation policies and scheduled overrides.

This API may be called a maximum of 2 times per second.

## Path parameters

- `user` string, required

## Headers

- `X-VO-Api-Id` string, required
- `X-VO-Api-Key` string, required

## Request body

- DeleteUserPayload — The information about what to do with the deleted user
  - `replacement` string — The user to take the place of the deleted user in escalations
  - `replacementStrategy` 'specifiedUser' | 'globalAdmin' | 'teamAdmin' | 'findReplacement' — The strategy you would like to use to replace the user. They work as follows specifiedUser - replace the deleted user with a specific user. If using this strategy, you MUST provide the `replacement` field as well. This is also the default strategy. So, if you provide no replacementStrategy in your request, you are still required to provide a `replacement` field. globalAdmin - replace the deleted user with the first Global Admin for the organization. teamAdmin - replace the deleted user in rotations/escalation policies with the team admin for the team related to that rotation or escalation policy. This strategy REQUIRES that every team have an admin that is not the deleted user. findReplacement - This strategy will attempt to find the best replacement based on roles within the team, paging policy configuration and other factors. Selected replacement user will be notified by email. You cannot delete the last active user on any team or last Global Admin user using this strategy.

## Response `200`

User was deleted

## Other responses

- `400` — Problem with the request arguments. The response payload may include an error message.
- `401` — Authentication parameters missing
- `403` — Authentication failed or rate-limit reached
- `404` — User not found
- `422` — There was a problem with the delete such as a replacement is required or the replacement user was not found. Details will be provided in the response body.
- `500` — Internal Server Error

---

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