Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Juniper Mist AI Orgs Psks API

A multi PSK (Pre-Shared Key) is a feature that allows the use of multiple PSKs for securing network connections.It provides a simple and comprehensive way to onboard client devices without relying on client mac addresses.Each psk has its own key name, which can be used for user-level accountability, key rotation, and visibility in the management platform. It supports the creation, rotation, and auto-expiration of PSKs, and allows vlan assignment and role assignment for dynamic per-user policies.Multi PSKs create virtual broadcast domains and can be used for end-user onboarding via authenticated sso login.Mist supports three methods of Org PSKs lookup: * local * radius * cloud

Juniper Mist AI Orgs Psks API is one of 211 APIs that Juniper Mist AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Orgs Psks. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 5 paths, and defines 19 schemas. It is described by OpenAPI 3.1.0, at version 2604.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.

9 operations 5 paths 19 schemas 1 DELETE2 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2604.1.1
Base URL
https://api.mist.com/api/v1
Authentication
API Key, HTTP Basic, API Key
License
Resource Areas
1

Authentication & Security 3

Juniper Mist AI Orgs Psks API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (apiToken). It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as X-CSRFToken (csrfToken). By default, every request must be authenticated.

  • apiToken — Like many other API providers, it’s also possible to generate API Tokens to be used (in HTTP Header) for authentication. An API token ties to a Admin with equa…
  • basicAuth — While our current UI uses Session / Cookie-based authentication, it’s also possible to do Basic Auth.
  • csrfToken — This protects the website against [Cross Site Request Forgery](https://en.wikipedia.org/wiki/Cross-siterequestforgery), all the POST / PUT / DELETE APIs needs…

Paths & Operations 9

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

Orgs Psks 9

A multi PSK (Pre-Shared Key) is a feature that allows the use of multiple PSKs for securing network connections. It provides a simple and comprehensive way to onboard client devic…

GET
/api/v1/orgs/{org_id}/psks
listOrgPsks
listOrgPsks 6 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/psks
createOrgPsk
createOrgPsk 2 params body → 200400401403404429
PUT
/api/v1/orgs/{org_id}/psks
updateOrgMultiplePsks
updateOrgMultiplePsks 1 param body → 200400401403404429
POST
/api/v1/orgs/{org_id}/psks/delete
deleteOrgPskList
deleteOrgPskList 1 param body → 200400401403404429
POST
/api/v1/orgs/{org_id}/psks/import
importOrgPsks
importOrgPsks 1 param body → 200400401403404429
DELETE
/api/v1/orgs/{org_id}/psks/{psk_id}
deleteOrgPsk
deleteOrgPsk 2 params → 200400401403404429
GET
/api/v1/orgs/{org_id}/psks/{psk_id}
getOrgPsk
getOrgPsk 2 params → 200400401403404429
PUT
/api/v1/orgs/{org_id}/psks/{psk_id}
updateOrgPsk
updateOrgPsk 2 params body → 200400401403404429
POST
/api/v1/orgs/{org_id}/psks/{psk_id}/delete_old_passphrase
deleteOrgPskOldPassphrase
deleteOrgPskOldPassphrase 2 params → 200400401403404429

Schemas 19

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

id
string
Unique ID of the object instance in the Mist Organization
psk_macs
array
If usage==macs, this list contains N number of client mac addresses or mac patterns(1122) or both. This list is capped at 5000
psk_usage
string
enum: macs, multi, single
response_http403
object
1 property
psk_id_list_psk_id
array
site_id
string
response_http404
object
1 property
psk_id_list
object
1 property
modified_time
number
When the object has been modified for the last time, in epoch
psks_import_file
object
1 property
response_http400
object
1 property
psks
array
response_http429
object
1 property
response_http401
object
1 property
psk_vlan_id
VLAN for this PSK key
org_id
string
psk_list
array
created_time
number
When the object has been created, in epoch
psk
object
PSK
23 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mist-ai-orgs-psks-api-openapi.yml Raw ↑

Other APIs Juniper Mist AI publishes across the network.

Juniper Mist WebSocket Streaming API
Juniper Mist Webhooks API
Juniper Mist AI Admins API
Juniper Mist AI Admins Login API
Juniper Mist AI Admins Login - OAuth2 API
Juniper Mist AI Admins Logout API
Juniper Mist AI Admins Lookup API
Juniper Mist AI Admins Recover Password API
Juniper Mist AI Constants Definitions API
Juniper Mist AI Constants Events API
Juniper Mist AI Constants Models API
Juniper Mist AI Installer API