---
title: "Remove phone numbers from a DIR"
method: DELETE
path: "/dir/{dir_id}/phone_numbers"
tags: ["Phone Numbers"]
---

# Remove phone numbers from a DIR

`DELETE /dir/{dir_id}/phone_numbers`

Deregister phone numbers from a DIR. The enterprise is resolved server-side from the DIR id. Returns a partial-success envelope.

## Path parameters

- `dir_id` string, uuid, required

## Request body

- BulkDeletePhoneNumbersRequest
  - `phone_numbers` string[], required

## Response `200`

Bulk-delete response. Inspect both `deleted` and `errors`.

- PhoneNumberBulkDeleteResponse — Bulk-delete partial-success response. `data` is the list of phone numbers that were soft-deleted. `meta.errors` holds per-number failures (e.g. number not associated with this DIR). When EVERY number in the request fails, the endpoint instead returns 400 with the canonical Telnyx error envelope and `data`/`meta` are absent.
  - `data` string[], required — Phone numbers that were successfully soft-deleted. Bare E.164 strings.
  - `meta` object, required
    - `errors` PhoneNumberItemError[], required — Per-number failures that did not block the call. Each entry has `phone_number`, `code`, `title`, `detail`.
      - `phone_number` string, required
      - `code` 'not_associated', required — Stable per-number error code. Currently only `not_associated` is emitted, when the number is not attached to this DIR.
      - `title` string, required
      - `detail` string, required

## Other responses

- `default` — An error occurred. The response carries the standard Telnyx error envelope.
- `4XX` — An error occurred. The response carries the standard Telnyx error envelope.

---

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