Represents an employee in HRIS

Represents the pages, posts, articles in a knowledge base

Represents the content of a page

Represents the high level grouping of pages in a knowledge base

Workspaces represent concepts like teams, workspaces, projects in apps that support them

Members are users, apps, bots and integrations part of the organization. To differentiate between the type of member, use the `type` attribute.

Channels are a way to group the communication happening between users in the source application. Channels can be used for group messaging, team messaging, etc.

Messages are the communication between users in the source application.

The Role object represents a role of a User.

The User object represents a User.

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

Licenses represent concepts like user seats in apps that support them

Workspaces represent concepts like teams, workspaces, projects in apps that support them

Drives is a collection of files and folders. They could have multiple Drive Items within them. Users could have multiple Drives accessible to them in a file storage system.

Drive Items are the files and folders present in a file storage system. These items are usually part of a Drive. You can differentiate between files and folders using the type attribute.

Users represent the people using the underlying file storage system.

Workspaces represent the top-level subdivision in a file storage system. They usually have their own set of drives, groups and users. Some of the usual terminologies used by the products for the top-l…

Permissions can answer your questions around which User has access to do what on a Drive Item or a Drive.

Applications represent the applications that are registered with the SSO service.

AppUsers represent the users assigned to an application.

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

Tickets and contacts 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. Yo…

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 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.

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…

Search endpoint for all the apps.