The Role object represents a role of a User.

The User object represents a User.

Organizations are the top level entity in the source application. Users are associated with an organization.

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.

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 Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status.

Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization.

Task Lists represent a collection of Tasks on a Ticket.

Task represent a smaller subdivision of a Ticket, which could be the list of things to do in a Ticket.

Organization represents the company or the entity using the ticketing system. An Organization can have one or more Workspaces and Users.

Search endpoint for all the apps.