---
title: "Delete Numbers from Inventory"
method: DELETE
path: "/restapi/v2/accounts/{accountId}/phone-numbers"
tags: ["Phone Numbers"]
---

# Delete Numbers from Inventory

`DELETE /restapi/v2/accounts/{accountId}/phone-numbers`

This method can only delete numbers that meet one of the following requirements:
  - numbers that have `"usageType": "Inventory"`
  - `"Forwarded"` numbers
  - `"Forwarded Company"` numbers

In other words, this method will not delete numbers which are in use on the account - extension direct numbers,
main number, etc. It is possible to indicate phone numbers to be deleted using their IDs or exact string values
in e.164 format. However, the same lookup method (by ID or by value) must be used for all numbers within the same API call.

## Path parameters

- `accountId` string, required

## Request body

- DeletePhoneNumbersRequest
  - `records` DeletePhoneNumbersRequestItem[], required — List of phone numbers or phone IDs to be deleted
    - `id` string — Internal unique identifier of a phone number
    - `phoneNumber` string — Phone number in e.164 format (with '+' prefix)

## Response `200`

Successful response

- DeletePhoneNumbersResponse
  - `records` DeletePhoneNumbersResponseItem[], required
    - `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
    - `id` string — Internal unique identifier of a phone number
    - `phoneNumber` string — Phone number in e.164 format (with '+' prefix)

## 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)