---
title: "Add Numbers to Inventory"
method: POST
path: "/restapi/v2/accounts/{accountId}/phone-numbers/bulk-add"
tags: ["Phone Numbers"]
---

# Add Numbers to Inventory

`POST /restapi/v2/accounts/{accountId}/phone-numbers/bulk-add`

Adds phone numbers to the account Inventory as unassigned. Currently, we support the following values: `Inventory`,
`InventoryPartnerBusinessMobileNumber` and `PartnerBusinessMobileNumber`. Later we may support some other values like `ForwardedNumber`, etc.

## Path parameters

- `accountId` string, required

## Request body

- AddPhoneNumbersRequest
  - `records` AddPhoneNumberRequestItem[], required — List of account phone numbers
    - `phoneNumber` string, required — Phone number in e.164 format (with '+' prefix). Wildcards are supported to pass large sets (for example 100 numbers); only one phone number record must be passed in request in that case, for example '+1650123456*'
    - `usageType` 'Inventory' | 'InventoryPartnerBusinessMobileNumber' | 'PartnerBusinessMobileNumber', required — Usage type of phone number. Currently, we support the following values: `Inventory`, `InventoryPartnerBusinessMobileNumber` and `PartnerBusinessMobileNumber`. Later we may support some other values like `ForwardedNumber`, etc.

## Response `200`

Successful response (synchronous operation)

- AddPhoneNumbersResponse
  - `records` AddPhoneNumbersResponseItem[], required — List of account phone numbers
    - `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, required — Phone number in e.164 format (with '+' prefix)

## Other responses

- `202` — Successful response (asynchronous operation)
- `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/revisions/8d602198ec97/schema)