Represents the pages, posts, articles in a knowledge base

Represents the content of a page

The contacts represent an existing point of contact at a company in a CRM.

The User object represents a User.

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

Licenses represent concepts like user seats in apps that support them

Workspaces represent concepts like teams, workspaces, projects 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.

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.

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.

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.

Search endpoint for all the apps.