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

Mist Orgs NAC Tags API

NAC Tags are the building blocks to compose nacrules.They can either appear in the "matching" / "not_matching" sections of a nacrule, in which case they play the role of classifiers, or they could appear in the "apply_tags" section of the of a nacrule, in which case they influence the result.When the "type" field of nactag is "match", it can be used as the classifier of a nacrule.- "match" field specifies the attribute name and "values" field specifies the list of attribute values to match on.- When multiple values are specified, its treated as an OR condition between those values. This behavior can be changed by setting "match_all" field to "true", in which case it is treated as an AND condition between those values.- By default, exact match is performed.This behavior can be changed as follows:- Adding `-` at the beginning will perform suffix match (ex: -staff will match foo-staff and bar-staff)- Adding `-` at the end will perform prefix match (ex: foo- will match foo-staff and foo-interns)- Adding `!` at both ends will perform substring match (ex: printer will match hp-printer-bldg1, brother-printer-lab)- Adding `!` at the beginning will perform negation of the match (ex: !ssid-guest will match any string that is not ssid-guest)- Note: when negation should be used along with suffix/substring operation, ! should always precede \* (ex: !guest will match any string that is not ending with guest)When the "type" field of nactag is NOT "match", it can be used as the result of a nacrule. "type" field identifies the action to take and the corresponding field would provide any associated parameters to that action. When the "type" field of nactag is NOT "match" and is any of the result type also supported by usermac table(`vlan`), "allow_usermac_override" field can be set to true to allow the override by usermac result

Mist Orgs NAC Tags API is one of 212 APIs that Mist publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Orgs NAC Tags. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 2606.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 20 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2606.1.1
Base URL
https://api.mist.com/api/v1
Authentication
API Key, API Key
License
Resource Areas
1

Authentication & Security 2

Mist Orgs NAC Tags 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](/operations/login) request, Mist returns a csrftoken cookie. Send…

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 Tags 5

NAC Tags are the building blocks to compose nacrules. They can either appear in the "matching" / "notmatching" sections of a nacrule, in which case they play the role of classifie…

GET
/api/v1/orgs/{org_id}/nactags
listOrgNacTags
listOrgNacTags 6 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/nactags
createOrgNacTag
createOrgNacTag 1 param body → 200400401403404429
DELETE
/api/v1/orgs/{org_id}/nactags/{nactag_id}
deleteOrgNacTag
deleteOrgNacTag 2 params → 200400401403404429
GET
/api/v1/orgs/{org_id}/nactags/{nactag_id}
getOrgNacTag
getOrgNacTag 2 params → 200400401403404429
PUT
/api/v1/orgs/{org_id}/nactags/{nactag_id}
updateOrgNacTag
updateOrgNacTag 2 params body → 200400401403404429

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are nac_tag (19 properties), response_http404 (1 property), response_http403 (1 property), response_http429 (1 property). Each schema is shown below with its type and property counts.

response_http403
object
Standard HTTP 403 permission error response
1 property
org_id
string
Unique identifier of a Mist organization
response_http400
object
Standard HTTP 400 bad request error response
1 property
nac_tag_type
string
enum: egressvlannames, gbptag, match, radiusattrs, radiusgroup, radiusvendorattrs, redirectnacportalid, sessiontimeout, usernameattr, vlan
nac_tag_username_attr
string
enum: automatic, cn, dns, email, upn
nac_tag_gbp_tag
If type==gbptag, GBP tag value returned by the NAC rule
nac_tag
object
NAC tag used as a rule-matching classifier or as a result attribute for allowed users
19 properties 2 required
nac_tag_radius_attrs
array
If type==radiusattrs, user can specify a list of one or more standard attributes in the field "radiusattrs". It is the responsibility of the user to provide a…
modified_time
number
When the object has been modified for the last time, in epoch
nac_tag_match
string
if type==match. enum: certcn, certeku, certissuer, certsan, certserial, certsub, certtemplate, clientmac, edrstatus, gbptag, hostname, idprole, ingressvlan, md…
nac_tag_radius_vendor_attrs
array
If type==radiusvendorattrs, user can specify a list of one or more vendor-specific attributes in the field "radiusvendorattrs". It is the responsibility of the…
response_http404
object
Standard HTTP 404 not found error response
1 property
response_http401
object
Standard HTTP 401 authentication error response
1 property
response_http429
object
Standard HTTP 429 rate limit error response
1 property
nac_tag_egress_vlan_names
array
If type==egressvlannames, list of egress vlans to return
id
string
Unique ID of the object instance in the Mist Organization
created_time
number
When the object has been created, in epoch
nac_tags
array
List of NAC tags
redirect_nacportal_id
string
If type==redirectnacportalid, the ID of the NAC portal to redirect to
nac_tag_values
array
If type==match, attribute values used by the NAC tag matcher

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mist-orgs-nac-tags-api-openapi.yml Raw ↑

Other APIs Mist publishes across the network.

Mist Admins API
Mist Admins Login API
Mist Admins Login - OAuth2 API
Mist Admins Logout API
Mist Admins Lookup API
Mist Admins Recover Password API
Mist Constants Definitions API
Mist Constants Events API
Mist Constants Models API
Mist Installer API
Mist MSPs Admins API
Mist MSPs API
Where this information came from

This is an independent, third-party profile of Mist Orgs NAC Tags 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.