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

Kaseya My Tickets API

The MyTickets API from Kaseya — 3 operation(s) for mytickets.

Kaseya My Tickets API is one of 488 APIs that Kaseya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include MyTickets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 3 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.bms.kaseya.com.

3 operations 3 paths 9 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.bms.kaseya.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Kaseya My Tickets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT Authorization header using the Bearer scheme.

Paths & Operations 3

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

MyTickets 3
GET
/v2/servicedesk/myticketsdeprecated
GetMyTickets 33 params → 200
POST
/v2/servicedesk/mytickets/search
SearchMyTickets body → 200
POST
/v2/clientportal/mytickets/search
SearchClientPortalMyTickets body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are MyTicketListDto (69 properties), ClientPortalTicketListDto (33 properties), MyTicketFilterDto (29 properties), ClientPortalMyTicketFilterDto (14 properties). Each schema is shown below with its type and property counts.

ClientPortalTicketListDtoListPagedResponse
object
4 properties
MyTicketFilterDto
object
29 properties
ErrorInfo
object
5 properties
ClientPortalTicketListDto
object
33 properties
MyTicketListDto
object
69 properties
ClientPortalMyTicketFilterDto
object
14 properties
ClientPortalMyTicketsInputDto
object
7 properties
MyTicketListDtoIEnumerablePagedResponse
object
4 properties
GetMyTicketsInputDto
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kaseya-mytickets-api-openapi.yml Raw ↑

Other APIs Kaseya publishes across the network.

IT Glue API
Kaseya VSA 9 REST API
Kaseya VSA 10 API
myITprocess API
Kaseya Account Codes API
Kaseya Account Invoice Settings API
Kaseya Accounts API
Kaseya Account Types API
Kaseya Action Types API
Kaseya Additional Invoice Field Values API
Kaseya Admin API
Kaseya Agent Procedure API
Where this information came from

This is an independent, third-party profile of Kaseya My 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.