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 MSPs 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.Support Tickets API Calls at the MSP level can be used to retrieve the tickets for each Organization attached to the MSP account.

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

Tagged areas include MSPs Tickets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 19 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.

2 operations 2 paths 19 schemas 2 GET

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 MSPs Tickets 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 2

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

MSPs Tickets 2

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/msps/{msp_id}/tickets
listMspTickets
listMspTickets 4 params → 200400401403404429
GET
/api/v1/msps/{msp_id}/tickets/count
countMspTickets
countMspTickets 3 params → 200400401403404429

Schemas 19

The contract defines 19 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.

response_http403
object
Standard HTTP 403 permission error response
1 property
response_http400
object
Standard HTTP 400 bad request error response
1 property
response_count
object
Distinct count response for time-bounded search results
6 properties 6 required
ticket_status
string
Ticket status. enum: closed, open, pending, solved. open means Mist is working on it, pending means requester attention is needed, solved means Mist considers…
count_results
array
List of count result rows
count_result
object
Count result row with the matching distinct field values
1 property 1 required
msp_tickets_count_distinct
string
enum: orgid, status, type
ticket
object
Support ticket record with status, comments, and metadata
10 properties 2 required
ticket_comments_attachment
object
Metadata for an attachment on a ticket comment
6 properties
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
id
string
Unique ID of the object instance in the Mist Organization
ticket_comments_attachments
array
List of attachment metadata objects for a ticket comment
tickets
array
Support ticket records returned by a ticket list response
ticket_comments_attachment_ids
array
List of ticket comment attachment identifiers
ticket_comment
object
Comment on a support ticket
5 properties 3 required
ticket_comments_attachment_id
string
Unique identifier for a ticket comment attachment
ticket_comments
array
List of comments on a support ticket

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mist-msps-tickets-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 MSPs Tickets 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.