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 SCEP API

The Orgs SCEP API from Juniper Networks — 3 operation(s) for orgs scep.

Juniper Networks Orgs SCEP 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 SCEP. 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 3 paths, and defines 11 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 3 paths 11 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 SCEP 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 3 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 SCEP 5
DELETE
/api/v1/orgs/{org_id}/setting/mist_scep
disableOrgMistScep
disableOrgMistScep 1 param → 200400401403404429
GET
/api/v1/orgs/{org_id}/setting/mist_scep
getOrgMistScep
getOrgMistScep 1 param → 200400401403404429
PUT
/api/v1/orgs/{org_id}/setting/mist_scep
updateOrgMistScep
updateOrgMistScep 1 param body → 200400401403404429
GET
/api/v1/orgs/{org_id}/setting/mist_scep/client_certs
listOrgIssuedClientCertificates
listOrgIssuedClientCertificates 9 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/setting/mist_scep/client_certs/revoke
revokeOrgIssuedClientCertificates
revokeOrgIssuedClientCertificates 1 param body → 200400401403404429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are org_setting_scep_response (7 properties), issued_client_certificate (6 properties), org_setting_scep (3 properties), issued_client_certificates_results (3 properties). Each schema is shown below with its type and property counts.

issued_client_certificate
object
Issued Mist SCEP client certificate metadata
6 properties
response_http403
object
Standard HTTP 403 permission error response
1 property
response_http400
object
Standard HTTP 400 bad request error response
1 property
response_http429
object
Standard HTTP 429 rate limit error response
1 property
client_cert_serial_numbers
object
Client certificate serial numbers targeted by a certificate operation
1 property
response_http401
object
Standard HTTP 401 authentication error response
1 property
org_setting_scep_response
object
Read-only Mist SCEP settings returned for the organization
7 properties
response_http404
object
Standard HTTP 404 not found error response
1 property
issued_client_certificates_results
object
Issued client certificate search results wrapper
3 properties
org_setting_scep
object
Mist SCEP settings for certificate enrollment
3 properties
org_setting_scep_cert_provider
string
enum: intune, jamf, byod

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

juniper-orgs-scep-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 SCEP 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.