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 Ticket Category Field Defaults Child API

The TicketCategoryFieldDefaultsChild API from Kaseya — 5 operation(s) for ticketcategoryfielddefaultschild.

Kaseya Ticket Category Field Defaults Child API is one of 488 APIs that Kaseya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TicketCategoryFieldDefaultsChild. 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 5 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://webservices2.autotask.net/ATServicesRest.

5 operations 5 paths 13 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.bms.kaseya.com
Resource Areas
1

Paths & Operations 5

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

TicketCategoryFieldDefaultsChild 5
GET
/V1.0/TicketCategories/{parentId}/FieldDefaults
TicketCategoryFieldDefaultsChild_Query 5 params → 200401403
GET
/V1.0/TicketCategories/{parentId}/FieldDefaults/{id}
TicketCategoryFieldDefaultsChild_QueryItem 6 params → 200401403
GET
/V1.0/TicketCategories/{parentId}/FieldDefaults/entityInformation
TicketCategoryFieldDefaultsChild_QueryEntityInformation 5 params → 200401403
GET
/V1.0/TicketCategories/{parentId}/FieldDefaults/entityInformation/fields
TicketCategoryFieldDefaultsChild_QueryFieldDefinitions 5 params → 200401403
GET
/V1.0/TicketCategories/{parentId}/FieldDefaults/entityInformation/userDefinedFields
TicketCategoryFieldDefaultsChild_QueryUserDefinedFieldDefinitions 5 params → 200401403

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are TicketCategoryFieldDefaultsModel (18 properties), Field (15 properties), FieldInformationModel (12 properties), EntityInformationModel (11 properties). Each schema is shown below with its type and property counts.

EntityInformationResultModel
object
1 property
UserDefinedFieldInformationResultModel
object
1 property
ItemQueryResultModel_TicketCategoryFieldDefaultsModel_TicketCategoryFieldDefaults
object
1 property
FieldInformationModel
object
12 properties
FieldInformationResultModel
object
1 property
PickListValue
object
7 properties
TicketCategoryFieldDefaultsModel
object
18 properties
Object
object
Field
object
15 properties
RestUserAccessLevel
object
EntityInformationModel
object
11 properties
QueryActionResult_TicketCategoryFieldDefaultsModel_TicketCategoryFieldDefaults
object
2 properties
PagingModel
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kaseya-ticketcategoryfielddefaultschild-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 Ticket Category Field Defaults Child 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.