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

Support tickets are a means for users to seek assistance and resolve issues they encounter with a product or service.They allow users to communicate their problems or questions to the Juniper Mist support team, who can then provide guidance, troubleshooting, or solutions.Support tickets typically include information such as the type of issue, relevant details, and any necessary attachments.

Juniper Mist AI Orgs Tickets 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 Tickets. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 6 paths, and defines 22 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.

8 operations 6 paths 22 schemas 4 GET3 POST1 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 Tickets 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 8

Across 6 paths, the API surfaces 8 operations — 4 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Orgs Tickets 8

Support tickets are a means for users to seek assistance and resolve issues they encounter with a product or service. They allow users to communicate their problems or questions t…

GET
/api/v1/orgs/{org_id}/tickets
listOrgTickets
listOrgTickets 4 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/tickets
createOrgTicket
createOrgTicket 1 param body → 200400401403404429
GET
/api/v1/orgs/{org_id}/tickets/count
countOrgTickets
countOrgTickets 3 params → 200400401403404429
GET
/api/v1/orgs/{org_id}/tickets/{ticket_id}
getOrgTicket
getOrgTicket 5 params → 200400401403404429
PUT
/api/v1/orgs/{org_id}/tickets/{ticket_id}
updateOrgTicket
updateOrgTicket 2 params body → 200400401403404429
POST
/api/v1/orgs/{org_id}/tickets/{ticket_id}/attachments
UploadOrgTicketAttachment
UploadOrgTicketAttachment 2 params body → 200400401403404429
GET
/api/v1/orgs/{org_id}/tickets/{ticket_id}/attachments/{attachment_id}
GetOrgTicketAttachment
GetOrgTicketAttachment 6 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/tickets/{ticket_id}/comments
addOrgTicketComment
addOrgTicketComment 2 params body → 200400401403404429

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are ticket (10 properties), response_count (6 properties), ticket_comments_attachment (6 properties), ticket_comment (5 properties). Each schema is shown below with its type and property counts.

id
string
Unique ID of the object instance in the Mist Organization
response_count
object
6 properties 6 required
tickets
array
response_http403
object
1 property
ticket_comments_attachment_id
string
ticket_comments_attachments
array
count_results
array
ticket_upload_attachments_file
object
1 property
count_result
object
1 property 1 required
response_http404
object
1 property
ticket_comments_attachment
object
6 properties
ticket_status
string
Ticket status. enum: open: ticket is open, Mist is working on it pending: ticket is open and Requester attention is needed (e.g. Mist is asking for some more i…
ticket
object
Support Ticket
10 properties 2 required
response_http400
object
1 property
response_http429
object
1 property
ticket_comment_import_file
object
2 properties
ticket_attachment
object
1 property
ticket_comment
object
5 properties 3 required
ticket_comments_attachment_ids
array
ticket_comments
array
response_http401
object
1 property
org_tickets_count_distinct
string
enum: status, type

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mist-ai-orgs-tickets-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