UtilitiesCommon

bounceDevicePort

POST
/api/v1/sites/{site_id}/devices/{device_id}/bounce_port

Port Bounce can be performed from Switch/Gateway.

Note: Ports starting with vme, ae, irb, and HA control ports (for SSR only) are not supported

The output will be available through websocket. As there can be multiple commands issued against the same AP at the same time and the output all goes through the same websocket stream, session is introduced for demux.

Subscribe to Device Command outputs

WS /api-ws/v1/stream

{    "subscribe": "/sites/{site_id}/devices/{device_id}/cmd"}
Example output from ws stream
{    "event": "data",    "channel": "/sites/4ac1dcf4-9d8b-7211-65c4-057819f0862b/devices/00000000-0000-0000-1000-5c5b350e0060/cmd",    "data": {        "session": "session_id",        "raw": "Port bounce complete."    }}

Authorization

Authorization<token>

Preferred authentication method for automation and integrations. Send the API token in the HTTP Authorization header.

Format: Authorization: Token {apitoken}

Notes:

  • An API token generated for a specific admin has the same privileges as that admin
  • An API token is automatically removed if it is not used for more than 90 days
  • SSO admins cannot generate admin API tokens. Use organization API tokens when scoped Org/Site privileges are needed.

In: header

Path Parameters

site_id*string
Formatuuid
device_id*string
Formatuuid

Request Body

application/json

Request Body

Request to bounce one or more device ports

ports?array<string>

Device ports to bounce

Response Body

curl -X POST "https://example.com/api/v1/sites/000000ab-00ab-00ab-00ab-0000000000ab/devices/000000ab-00ab-00ab-00ab-0000000000ab/bounce_port" \  -H "Content-Type: application/json" \  -d '{    "ports": [      "ge-0/0/0",      "ge-0/0/1"    ]  }'
Empty