Reboot user device

POST

/domains/{domain}/users/{user}/devices/{device}/reboot

Last modified:2026-09-27 20:50:13

OperationId:RebootDeviceForUser

Asks the device to fetch its configuration again and reboot, by publishing a SIP NOTIFY with the check-sync event.

Requires Basic User for your own devices, or Site Manager, Office Manager, Reseller, or Super User for the users you administer. A Site Manager can reboot only devices of users in its own site. It uses the same privilege as a device update.

The reboot request was published, not delivered. The API publishes it over the service bus (SBUS) and the core sends the phone a SIP NOTIFY. Nothing reports back: a phone that is off or not registered never sees it, and the answer is the same. Any other device field in the body is applied as an update first, and the reboot follows it.

A device that does not exist returns 404. A full SIP URI in the path must name the path domain; a device in another domain returns 404. A device that belongs to a different user returns 404. A Basic User or other user-level scope rebooting someone else's device, or a Site Manager rebooting a device outside its site, gets 403. POST /domains/{domain}/devices/reboot reboots several devices at once.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

The reboot request was published. Delivery to the phone is not confirmed.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

🟠405Method Not Allowed

Request Example

Shell

JavaScript

Java

Swift

cURL

Plain rebootVendor event

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/example.com/users/1001/devices/1001a/reboot' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'

Response Example

202 - Accepted

The reboot request was published.

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-09-27 20:50:13

List territory devices

Reboot domain device