Group in the docs Paths and operations Read closely
Tickets /api/v2/tickets: create, view, update, list, delete and restore, plus forward, merge, associations and bulk update or delete at /tickets/bulk_update and /tickets/bulk_delete. Status and priority are numbers, not labels. Embedding related data with include costs extra calls from your per-minute budget.
Conversations /tickets/{id}/reply for a public reply, /tickets/{id}/notes for a note (public or private), and a list call for the whole thread. A reply emails the requester. Use a private note when the integration is only recording something for agents.
Contacts and companies /api/v2/contacts and /api/v2/companies: create, view, list, update, delete, plus merge, import and export. Contacts also have autocomplete search and a filter call. Contacts have soft and hard delete. A soft-deleted contact can be restored; a hard delete is permanent.
Time entries /tickets/{id}/time_entries per ticket and /api/v2/time_entries for everything, including starting and stopping a timer. Useful for billing exports. Pull by date range rather than ticket by ticket.
Ticket fields /api/v2/ticket_fields to read definitions, /api/v2/admin/ticket_fields to change them, along with sections and forms. Read this at startup and map custom fields by their internal names. Labels change; internal names don't.
Filter tickets /api/v2/search/tickets?query= with a URL-encoded query up to 512 characters, supporting greater-than and less-than on dates and numbers. Results are capped and archived tickets aren't included. For bulk pulls, list with updated_since instead.