The Role object represents a role of a User.

The User object represents a User.

Groups are a collection of users in the source application. In some applications, they might also be called Teams.

Activities are the actions performed by users in the source application.

Utilization object represents utilization reports.

Licenses represent concepts like user seats in apps that support them

Attachments are the files associated with a ticket or a comment.

Tickets can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection.

Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments.

Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them.

Teams represent the grouping system used for Users. These are usually called groups, teams, agent groups, etc. in the underlying products. A User can belong to one or more Teams.

Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product.

Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc.

Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Ticket, Contact, etc. is_user_defined attribute within Field can be used to differentiate between custom and system defined Fields.

Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status.

Ticket Priorities represent the intended order in which the Tickets should be worked on. Some products provide customizing the Ticket Priorities.

Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc.

Search endpoint for all the apps.