RADIUS API
The RADIUS API covers the parts of Airgate’s RADIUS service that you manage over REST: the machine-authentication cache that lets a user sign-in inherit [Machine Authenticated], and per-node RADIUS statistics for platform administrators. RADIUS, RadSec and EAP traffic itself is not part of the REST API; network devices send it to Airgate’s RADIUS service, and the results appear on Monitor › Sign-in log (see the Insight API).
Base path and permissions
Section titled “Base path and permissions”Tenant routes are relative to /api/v1/t/{tenant}, where {tenant} is the tenant slug or ID. The platform route is under /api/v1/platform. See API overview for authentication.
| Method | Path | Permission | Purpose |
|---|---|---|---|
GET |
/radius/machine-auth |
identity:read |
List valid machine-authentication entries |
DELETE |
/radius/machine-auth |
identity:write |
Clear the tenant’s machine-authentication cache |
DELETE |
/radius/machine-auth/{mac} |
identity:write |
Forget one device |
GET |
/api/v1/platform/radius/stats |
platform:admin |
RADIUS route counters and database pool of the node that answers |
The RADIUS service also talks to the Airgate core over internal endpoints. They are not exposed to API clients.
Machine-authentication cache
Section titled “Machine-authentication cache”When a computer authenticates with its machine account (identity host/<name>, as the PEAP or TTLS inner identity, or an EAP-TLS machine certificate whose CN is the computer’s FQDN), Airgate stores the device MAC address before it sends the Access-Accept. A later user sign-in from the same MAC gets Authentication:Machine = true, so the user has both [User Authenticated] and [Machine Authenticated] roles.
Entries last for the tenant setting machine_auth_cache_hours (default 24; 0 disables the cache). Expired entries are removed every hour.
GET /radius/machine-auth
Section titled “GET /radius/machine-auth”Permission: identity:read
| Query | Meaning |
|---|---|
q |
MAC address in any notation, or a substring of the machine name |
limit, offset |
Paging (default 50, at most 1000) |
Valid entries, newest first.
curl -s "$AIRGATE/api/v1/t/$TENANT/radius/machine-auth?q=pc1" \ -H "Authorization: Bearer $TOKEN"{"items": [{"mac": "02:00:00:00:03:01", "machine_name": "host/pc1.contoso.com", "nad_id": "5415...", "service_name": "Corp 802.1X", "auth_source": "Contoso AD", "authenticated_at": "2026-10-29T18:01:33Z", "expires_at": "2026-10-30T18:01:33Z"}], "total": 1}DELETE /radius/machine-auth
Section titled “DELETE /radius/machine-auth”Permission: identity:write
Clears the tenant’s whole cache. Returns 204. Audited (action clear, object type machine_auth_cache). Users who sign in afterwards do not get [Machine Authenticated] until their computer authenticates again.
DELETE /radius/machine-auth/{mac}
Section titled “DELETE /radius/machine-auth/{mac}”Permission: identity:write
Forgets one device. {mac} is a MAC address in any notation. Returns 204; 404 when the device has no entry; 400 for an invalid MAC. Audited.
curl -s -X DELETE "$AIRGATE/api/v1/t/$TENANT/radius/machine-auth/02-00-00-00-03-01" \ -H "Authorization: Bearer $TOKEN"Statistics
Section titled “Statistics”GET /api/v1/platform/radius/stats
Section titled “GET /api/v1/platform/radius/stats”Permission: platform:admin
Counters of the node that answers, since it started. Each route (authorize, inner-authorize, authenticate, eap-tls-cert, radsec-connect, post-auth, accounting) has calls, 2xx, 4xx, 5xx, panics, avg_ms, max_ms, p50_ms and p99_ms. The response also carries conversations (EAP conversations in memory), effects_queued, effects_overflow and effects_workers (post-decision work such as CoA and device updates), and db_pool (the node’s database connection pool).
{"routes": {"authorize": {"calls": 120, "2xx": 101, "4xx": 19, "5xx": 0, "panics": 0, "avg_ms": 3, "max_ms": 31, "p50_ms": 2, "p99_ms": 25}}, "conversations": 57, "effects_queued": 0, "effects_overflow": 0, "effects_workers": 16, "db_pool": {"max_conns": 64, "total_conns": 23, "acquired_conns": 2, "idle_conns": 21, "acquire_count": 5120, "empty_acquire_count": 3, "empty_acquire_wait_ms": 12, "canceled_acquire_count": 0, "acquire_ms": 40}}A growing empty_acquire_wait_ms under load means requests wait for a free database connection. See High availability and sizing and Metrics and monitoring.