Skip to content
Hausing Hausing API Documentation

General Ticket Chat

The API provides endpoints to:

Chat file endpoints are covered in Ticket Chat Files.

Chat participant model

Section titled “Chat participant model”

When working with chats, the commonly used model is TicketChatParticipantModel (or TicketChatCreateParticipantModel when creating a new chat).

The following properties identify chat participants:

  • watcherEmail — the participant is an external email and cannot be placed in any of the following categories
  • userId — either a management or tenant user
  • crmCompanyId — a CRM contractor
  • crmCompanyContactId — a CRM contractor contact; every contact can see all contractor chats
  • buildingId — used for building-based ticketing links generated for non-users. The buildingId serves as the participant key for chats to and from that view
  • hausingCompanyId — used to synchronize chats between contractors that are also Hausing client companies. In normal cases, this should not be used by external integrators

participantGroupType

Section titled “participantGroupType”

Only available on TicketChatCreateParticipantModel. Used to create a chat where the management user receiver participant is still unknown (ticket supervisor is not yet assigned).