Changes where calls to one phone number go, or its other settings. Requires Site Manager, Office Manager, Reseller, or Super User scope. Scopes below Reseller change only their own domain, and a Reseller only the domains in its territory.The request is a partial update: a field you leave out keeps its value. A 202 means the change is accepted and applied shortly after, so a read made right away can still show the old values.A Reseller or Super User can name a number that is not assigned to any domain. The change assigns it to the domain in the path. A Super User can also name a number assigned to another domain, and the change moves it to the domain in the path, so check the path before you send.A number that has only an SMS assignment can be changed too. Send only sms-* fields to change the assignment, or dial-rule-translation-destination-user to give the number a dial rule.If an Office Manager sends dial-rule-translation-destination-host, it must be its own domain, except with the to-connection and to-single-device applications, or the request answers 403. A number in neither place answers 404: add it with POST /domains/{domain}/phonenumbers.For a worked example of each routing case, see PUT /domains/{domain}/phonenumbers. You do not need to send phonenumber in the body. If you do, it must match the path.
Request
Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Path Params
Body Params application/json
Examples
Responses
🟢202Accepted
application/json
The change is accepted and applied shortly after this response.