How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Juniper Networks Orgs NAC Rules API

The NAC Rules (or Auth Policies) are a set of rules that devices and users must fulfill in order to gain access to the network and use network resources.Juniper Mist Access Assurance evaluates authentication requests based on the specified policy conditions. If a user or device satisfies the conditions, Mist Access Assurance applies actions that either allow or deny access to the user or device.These actions can also apply attributes such as VLAN and role to the allowed users. Mist Access Assurance uses "NAC Tags" (or Auth Policy Labels) as the policy matching criteria and as a policy action for allowed users. NAC Tags can be managed with the [Orgs NAC Tags API Calls]($h/Orgs%20NAC%20Tags/_overview)

Juniper Networks Orgs NAC Rules API is one of 263 APIs that Juniper Networks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Orgs NAC Rules. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, and rate-limit docs.

This API exposes 5 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 2607.1.1.

Requests are made against 12 base URLs: https://api.mist.com, https://api.gc1.mist.com, https://api.ac2.mist.com, https://api.gc2.mist.com, https://api.gc4.mist.com, https://api.eu.mist.com, https://api.gc3.mist.com, https://api.ac6.mist.com, https://api.gc6.mist.com, https://api.ac5.mist.com, https://api.gc5.mist.com, https://api.gc7.mist.com.

5 operations 2 paths 12 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2607.1.1
Base URL
netconf://[device-ip]:830
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Juniper Networks Orgs NAC Rules API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (apiToken). An API key is passed in the header as X-CSRFToken (csrfToken). By default, every request must be authenticated.

  • apiToken — Preferred authentication method for automation and integrations. Send the API token in the HTTP Authorization header. Format: Authorization: Token {apitoken} N…
  • csrfToken — Session-based authentication for browser or login/password flows. After a successful [Login]($e/Admins%20Login/login) request, Mist returns a csrftoken cookie.…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Orgs NAC Rules 5

The NAC Rules (or Auth Policies) are a set of rules that devices and users must fulfill in order to gain access to the network and use network resources.

GET
/api/v1/orgs/{org_id}/nacrules
listOrgNacRules
listOrgNacRules 3 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/nacrules
createOrgNacRule
createOrgNacRule 1 param body → 200400401403404429
DELETE
/api/v1/orgs/{org_id}/nacrules/{nacrule_id}
deleteOrgNacRule
deleteOrgNacRule 2 params → 200400401403404429
GET
/api/v1/orgs/{org_id}/nacrules/{nacrule_id}
getOrgNacRule
getOrgNacRule 2 params → 200400401403404429
PUT
/api/v1/orgs/{org_id}/nacrules/{nacrule_id}
updateOrgNacRule
updateOrgNacRule 2 params body → 200400401403404429

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are nac_rule (13 properties), nac_rule_matching3 (10 properties), nac_rule_matching1 (10 properties), response_http401 (1 property). Each schema is shown below with its type and property counts.

response_http403
object
Standard HTTP 403 permission error response
1 property
nac_auth_type3
string
NAC authentication method that must match the request. enum: cert, device-auth, eap-teap, eap-tls, eap-ttls, idp, mab, eap-peap.
response_http400
object
Standard HTTP 400 bad request error response
1 property
response_http429
object
Standard HTTP 429 rate limit error response
1 property
response_http401
object
Standard HTTP 401 authentication error response
1 property
nac_rule_action2
string
Allow or block decision applied when the NAC rule matches
response_http404
object
Standard HTTP 404 not found error response
1 property
nac_rule_matching3
object
Criteria that must match for the NAC rule to apply
10 properties
nac_rule
object
NAC authentication policy rule that matches request criteria and applies an allow or block action
13 properties 2 required
nac_rule_matching1
object
Criteria that must not match for the NAC rule to apply
10 properties
nac_rule_guest_auth_state2
string
Guest portal authorization state condition for the rule. enum: authorized, unknown.
nac_rule_matching_port_type
string
Port attachment type matched by a NAC rule. enum: wired, wireless

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

juniper-orgs-nac-rules-api-openapi.yml Raw ↑

Other APIs Juniper Networks publishes across the network.

Junos PyEZ (Python API)
JSNAPy API
Juniper Networks Allowlists and Blocklists API
Juniper Networks Analytics API
Juniper Networks Audit Logs API
Juniper Networks Authentication API
Juniper Networks BGP Routers API
Juniper Networks Blueprints API
Juniper Networks Clients API
Juniper Networks Configlets API
Juniper Networks Configuration API
Juniper Networks Connectivity Templates API
Where this information came from

This is an independent, third-party profile of Juniper Networks Orgs NAC Rules API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.