Reboot domain devices in bulk

POST

/domains/{domain}/devices/reboot

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

OperationId:RebootDevicesBulk

Asks every device named in device-list to fetch its configuration again and reboot. This is the bulk form of POST /domains/{domain}/devices/{device}/reboot.

Requires Office Manager, Reseller, or Super User, in your own domain or one you administer.

Every name is checked before anything is sent: a full SIP URI in another domain returns 404 and nothing is rebooted. Then one reboot request is published over the service bus (SBUS) per device, and the answer is 202. A name with no device is not an error: it is published and nothing receives it. Check the names with GET /domains/{domain}/devices first if that matters. Delivery to each phone is not confirmed.

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/jsonRequired

Examples

Responses

🟢202Accepted

application/json

One reboot request was published per name. Delivery is not confirmed.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠405Method Not Allowed

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

cURL

Two devicesComma-separated

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

Response Example

202 - Accepted

Both reboot requests were published.

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

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

Reboot domain device

List domain device summaries