---
title: "Delete User Extensions"
method: DELETE
path: "/restapi/v2/accounts/{accountId}/extensions"
tags: ["User Settings"]
---

# Delete User Extensions

`DELETE /restapi/v2/accounts/{accountId}/extensions`

Deletes user extension(s) and either keeps or destroys the assets - numbers and devices.
Multiple extensions can be deleted with a single API call.

**Please note:** This API cannot be tested on Sandbox.

## Path parameters

- `accountId` string, required

## Request body

- BulkDeleteUsersRequest
  - `keepAssetsInInventory` boolean — Indicates that the freed users' assets (phone numbers and devices) should be moved to account inventory rather than deleted. If set to `true`, the phone numbers and devices assigned to deleted extensions will be kept in the account's inventory. If set to `false`, these assets will be deleted from the account and returned to either the partner's phone numbers or RingCentral's phone number pool
  - `records` BulkOperationExtensionReference[], required
    - `id` string, required — Internal identifier of a RingCentral extension

## Response `200`

Successful response

- BulkDeleteUsersResponse
  - `records` object[], required
    - `id` string — Internal identifier of an extension
    - `bulkItemSuccessful` boolean, required — Indicates if this item was processed successfully during bulk operation. If false, `bulkItemErrors` attribute contains the list of errors
    - `bulkItemErrors` ApiError[] — The list of errors occurred during processing of particular item of bulk operation. Returned only if `bulkItemSuccessful` is false
      - `errorCode` string, required — Logical error code (typically, 3 letters followed with number, dash separated)
      - `message` string, required — User-friendly error message

## Other responses

- `400` — General response with **HTTP 400 "Bad request"** status.<br> Reasons: unparsable request, path, query or body parameters are invalid. The error description may contain reference to particular parameter(s) which haven't passed the validation.
- `403` — General response with **HTTP 403 "Forbidden"** status.<br> Reasons: the requested operation is forbidden because of certain resource state, lack of permissions, feature unavailability, etc.
- `404` — General response with **HTTP 404 "Not found"** status.<br> Reasons: the entity with given ID (typically specified in a path parameter), is not found or inaccessible
- `429` — General response with **HTTP 429 "Too many requests"** status.<br> Reasons: certain rate limit is exceeded.
- `500` — General response with **HTTP 500 "Internal Server Error"** status.<br> Reasons: general server-side error.
- `503` — General response with **HTTP 503 "Service not available"** status.<br> Reasons: server cannot process the request because of being overloaded, misconfiguration or other issues.

---

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