The repo represent a repository in the CI/CD.

The branch represent a branch in the CI/CD.

The build represent a build in the CI/CD.

The job represent a job in the CI/CD.

The artifact represent an artifact in the CI/CD.

The workflow represent a CI/CD workflow.

The Workspace object is used to represent a workspace within a company.

Accounts represent the companies or organizations that you are in contact with. Accounts have one or more Contacts associated with them.

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

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.

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

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

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