---
title: "Reboot an AP Swarm"
method: POST
path: "/network-troubleshooting/v1/aps/{serial-number}/rebootSwarm"
tags: ["Access Points"]
---

# Reboot an AP Swarm

`POST /network-troubleshooting/v1/aps/{serial-number}/rebootSwarm`

## Request

- Base URL: `https://sso.common.cloud.hpe.com`
- URL: `https://sso.common.cloud.hpe.com/network-troubleshooting/v1/aps/{serial-number}/rebootSwarm`
- Auth: OAuth 2
  - Client credentials
  - Token URL: `https://sso.common.cloud.hpe.com/as/token.oauth2`
- TypeScript: <https://skmtc.dev/arubanetworks/apis/authorization/docs/network-troubleshooting/v1/aps/:serial-number/rebootSwarm/post.ts> (a function with typed inputs; its response is checked against the schema)

Initiates a reboot operation on the entire Swarm, triggered via its current conductor AP. The {serial-number} must be the serial of the Swarm's active conductor.

## Path parameters

- `serial-number` string, required

## Response `202`

Accepted. The Swarm reboot action has been successfully initiated.

- ActionInitiatedStatus
  - `startTime` string, date-time, required: ISO 8601 timestamp indicating when the action was initiated.
  - `status` 'INITIATED', required: The initial status of the action.

## Other responses

- `400`: Bad Request. Validation errors, or the specified device is not a conductor.
- `401`: Unauthorized. Authentication credentials are required or invalid.
- `403`: Forbidden: Access is denied.
- `404`: Not Found. The device with the specified serial number was not found.
- `409`: Conflict. The device is already performing a reboot.
- `429`: Too Many Requests. The user has sent too many requests in a given amount of time.
- `500`: Internal Server Error. An unexpected error occurred on the server.

---

[API](https://skmtc.dev/arubanetworks/apis/authorization.md) - [All operations](https://skmtc.dev/arubanetworks/apis/authorization/llms.txt) - [OpenAPI document](https://skmtc.dev/arubanetworks/apis/authorization/revisions/74c95058b11f?raw)