Reboot Device

POST

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

Last modified:2026-08-21 05:44:25

OperationId:RebootDevice

Ask the endpoint to re-provision itself — a SIP NOTIFY carrying the check-sync Event header, which every mainstream desk phone answers by re-fetching its configuration and rebooting.

This is the v2 path for the check-sync parameter the v1 device update has always accepted (API-2129). PUT .../devices/{device} still honours check-sync: yes, but on that path the reboot replaces the update — no other field in the same body is applied — so a dedicated path is the safer way to ask for it.

The API publishes the request onto the service bus and answers 202 Accepted. Delivery to the phone is asynchronous and unacknowledged: a device that is powered off or unregistered simply never sees it, and that is not reported back here.

Requires the same update privilege on the device as an ordinary device update.

Domain-scoped form — identical behaviour; the device's owner is resolved from the device itself, so the user does not have to be named in the path.

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

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --globoff 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/{{domain}}/devices/{{user}}a/reboot' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "check-sync-event-header": "check-sync;reboot=true"
}'

Response Example

202 - Example 1

{
    "code": 0,
    "message": "string"
}

Modified at 2026-08-21 05:44:25

Reboot Device for User

Reboot Devices in Bulk