### Fetch one NAS

`GET /api/v1/admin/nas/{id}`

The full device record, including tunnel and operator-VPN configuration.

- Authentication: manager session (JWT) or API token
- Permission: `prm_nas_index` (View NAS)
- Risk: read

#### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | integer | yes | NAS id. |

#### Errors

| Code | Status | When |
| --- | --- | --- |
| `ERR_NOT_FOUND` | 404 | no such NAS in this tenant |

#### Note

Read tunnel_transport to decide how to render a device, never "whichever tunnel IP is non-null". A NAS keeps its standby allocations after switching transport, so more than one of wg_tunnel_ip, ovpn_tunnel_ip and sstp_tunnel_ip is set on any device that ever changed. active_tunnel_ip is the database's own resolution of that question.