RadiusServers
Search RadiusServers
Search and list RadiusServer records with filtering, sorting, and pagination.
GET
Search RadiusServers
A RADIUS server is a hosted Wi-Fi authentication network that a location rents through the built-in provider integration, so customers sign in to the Wi-Fi with their Nexudus account and their network sessions become check-ins. Creating a record is not a settings change: the backend calls the provider to build a real network, a captive portal for the selected Vendor, and an authentication endpoint, then stores the returned network, portal, splash-page, IP, port and shared-secret values as read-only fields the operator copies into their wireless controller. It fails unless the location has a RADIUS licence key configured. Deleting a record deletes the network and captive portal at the provider and cannot be undone. Only the first active server of a location is used, an active server is billed monthly, and a server that is not active is skipped by the 15-minute synchronisation. The record alone does not grant anyone Wi-Fi access; that depends on each customer allowing network check-in and holding a pass that allows it.
Authentication
This endpoint requires OAuth2 authentication. Include a valid bearer token in the
Authorization header.
The authenticated user must be a full unrestricted administrator or have the RadiusServer-List role.Enums
eRadiusServerVendor — Vendor values
eRadiusServerVendor — Vendor values
Query Parameters
Pagination & Sorting
Filters
Filter by iD of the location that owns this RADIUS server. The location’s RADIUS licence key setting decides whether the server can be provisioned at all, and its country selects the hosting region: US, AU, or Europe for everywhere else..
Filter by operator-facing label for this server in the location’s list. The provider-side network and captive portal are named automatically from the location name and the creation date, so this value is not sent to the provider..
Filter by wireless hardware or controller the captive portal is built for, such as Meraki_Sign_On, Ubiquiti_Networks, MikroTik or Ruckus_Wireless; use Other when the vendor is not listed. It is applied only while the captive portal is provisioned during creation, so changing it afterwards does not rebuild the portal and the admin form disables it once the record exists..
Filter by whether this server is included in the RADIUS synchronisation that runs every 15 minutes to import provider accounting data as customer check-ins. Only the first active server of a location is used, and an active server also adds a RADIUS line to the location’s monthly invoice. Set false to stop syncing and billing without tearing down the provisioned network..
Filter by optional free-text note about this server. It is not shown on the admin form and is not sent to the provider..
Filter by legacy provider customer identifier that no backend code ever populates, so it is always empty. Hidden from the agent because it would be misleading; use NetworkId to identify the provisioned network..
Filter by read-only identifier of the hosted RADIUS network created by the provider when this record was saved. Deleting the record deletes that network at the provider; it cannot be set or changed..
Filter by read-only identifier of the captive portal created alongside the network at creation time, using the selected Vendor. Deleting the record deletes the portal at the provider; it cannot be set or changed..
Filter by read-only public identifier the provider generates for the captive portal’s splash page. It appears in the customer-facing Wi-Fi login URL and cannot be set or changed..
Filter by read-only primary RADIUS server IP address supplied by the provider at creation. The operator enters it in the wireless controller’s RADIUS settings; it cannot be set or changed here..
Filter by read-only backup RADIUS server IP address supplied by the provider at creation, used when the primary address is unreachable. It cannot be set or changed here..
Filter by read-only RADIUS accounting port supplied by the provider at creation. The wireless controller sends accounting packets here, which become customer check-ins on the next synchronisation..
Filter by read-only RADIUS authentication port supplied by the provider at creation. The wireless controller sends authentication requests here..
Filter by credential the wireless controller uses to authenticate to the RADIUS server, issued by the provider at creation. Hidden from the agent because it is a secret; the operator must read it from the location’s RADIUS settings page in the admin panel..
Range Filters
Code Examples
Simple listing
Filtering by Name
Range filters
Response
200
The list of RadiusServer records matching the query. See the Get one RadiusServer endpoint for the full list of properties returned for each record.
Example Response