Reboot domain device

POST

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

Last modified:2026-09-27 20:52:23

OperationId:RebootDevice

Asks the device to fetch its configuration again and reboot, without naming its owner. It publishes a SIP NOTIFY with the check-sync event.

Requires Office Manager, Reseller, or Super User, in your own domain or one you administer. It uses the same privilege as a device update. Basic User and Site Manager reboot through POST /domains/{domain}/users/{user}/devices/{device}/reboot.

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, or a full SIP URI in another domain, returns 404.

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/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:52:23

Reboot user device

Reboot domain devices in bulk