---
title: "Set a number's voice-side assignee"
method: PATCH
path: "/voice/numbers/assignee"
tags: ["Phone Numbers"]
---

# Set a number's voice-side assignee

`PATCH /voice/numbers/assignee`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/voice/numbers/assignee`
- Auth: HTTP bearer

Point a number's voice-side assignment at someone else.

The VOICE half of `PATCH /phone-numbers/update-assignee`, which does this
and updates the CDP record. Published separately because the app's
propagation to voice is best-effort and only logs a warning when it fails -
so the two records can disagree, and this is the way to reconcile them
without re-running the whole reassignment.

Sending `assigned_to: ""` clears the assignment. Assigning a WORK number
also creates the person's phone-directory row, which is what makes them
findable by name to the receptionist.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- VoiceAssigneeRequest: Point a number's voice-side assignment at someone else. Mirrors `graph8_livekit.schemas.numbers.UpdateAssignee` minus `org_id`. `assigned_to` is REQUIRED but may be the empty string, which is how voice spells "clear the assignment" - its own normalisation passes falsy input through untouched for exactly that reason.
  - `number` string, required: The number to reassign, E.164.
  - `assigned_to` string, required: Email of the new assignee, or `""` to clear it. Normalised by voice before storage so inbound ring targeting, the dialer assignee filter and per-rep stat redaction all compare equal.

## Response `200`

Successful Response

- ApiResponsePhoneNumberPayload
  - `data` PhoneNumberPayload, required: An open envelope for a purchase result, a release, or an A2P job. Open on purpose. A purchase returns the stored row (whose capability and provider-metadata keys differ per provider), a workflow start returns a `workflow_id`, and the A2P reconcile returns per-number outcomes that grow as carriers add statuses. Pinning it would silently drop whatever the provider reported that this contract had not caught up on.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)