# reboot activity — NCM API

Reboots a device or a whole group of devices. Write-only: a single POST triggers the reboot and there is no collection to read back, so confirm the outcome through router state samples or the device's online status.

Base URL: https://www.cradlepointecm.com/api/v2

## Authentication

This is a v2 endpoint (`/api/v2/` path). Every request requires ALL FOUR API-key headers:

| Header | Description |
| --- | --- |
| X-CP-API-ID | Cradlepoint API ID |
| X-CP-API-KEY | Cradlepoint API key |
| X-ECM-API-ID | ECM API ID |
| X-ECM-API-KEY | ECM API key |

Keys are generated in the NCM UI under API Keys, separately from v3 tokens. The v2 and v3 auth schemes are NOT interchangeable: a v3 Bearer token is rejected on v2 endpoints.

### POST /reboot_activity/

Create a reboot_activity record

<p>This operation reboots a device or a group of devices.</p>

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| X-ECM-API-ID | header | string | yes | <strong>ECM API app Id</strong> |
| X-ECM-API-KEY | header | string | yes | <strong>ECM API app key</strong> |
| X-CP-API-ID | header | string | yes | <strong>Cradlepoint API app Id</strong> |
| X-CP-API-KEY | header | string | yes | <strong>Cradlepoint API access key</strong> |

**Request body**

**Example request**

```bash
curl -X POST "https://www.cradlepointecm.com/api/v2/reboot_activity/" \
  -H "X-CP-API-ID: <cp-api-id>" \
  -H "X-CP-API-KEY: <cp-api-key>" \
  -H "X-ECM-API-ID: <ecm-api-id>" \
  -H "X-ECM-API-KEY: <ecm-api-key>" \
  -H "Content-Type: application/json" \
  -d '{ ... }'
```

**Response 200** — Example response.

```json
{
  "group": "https://www.cradlepointecm.com/api/v2/groups/24/"
}
```