Skip to main content
This document contains a reference of data structures available in the Agent Chat API. Here, you can review the object fields, as well as sample responses for the event, user, and other common structures. The reference applies both to the Web and RTM APIs.

Events

One of the data structures are events. They are sent to a chat via the send_event method. Apart from events, there are also Properties, Users, and Other common data structures. These are the available event types:

File

The File event indicates about an uploaded file. Request Response
Sample File in response

Form

The Form event contains an empty form to be filled out by the customer. It doesn’t matter how the form is configured or what fields it has — it can be any event of type form. Currently, the Form events are not supported natively in Text, but you can leverage this feature in a custom chatting solution. Request Response A sample use case: sending a form in the chat after a pre-determined agent’s inactivity period. This could be a way of gathering contact info from customers so that the overloaded agent can contact them later.
Sample Form in response

Filled form

The Filled form event contains data from a form (prechat or postchat survey). Request Response
Sample Filled form in response

Message

The Message event contains a text message to other chat users. Request Response
Sample Message in response

Rich message

Rich message (RM) event contains a rich message data structure. Request Response
Sample Rich message in response

Custom

Custom event is an event with customizable payload. Request Response
Sample Custom event in response

System message

System message event is a native system event sent in specific situations. Request Response
Sample System message in response

System

System event is an extension and a future replacement for System message. Similarly, it is a native system event sent in specific situations. Request It is not possible to send a System event in API version 3.6. Response
Sample System event in response

Users

Users are another important data structure. Within this data structure type, we can distinguish:

Agent

Sample agent data structure

My profile

Sample My profile data structure

Customer

Sample Customer data structure

Cart

Cart Item

Customer Property

Customer properties are identified by the UUID generated in the Create customer property definition method. The property’s type is set on creation.

Other common structures

Apart from Events and Users, there are also other common data structures you might work with. Those are:

Access

Sample Access data structure

Chats

Sample chat data structure

Chat summaries

Chat summary is similar to the chat data structure. The difference is that chat contains a thread object, while chat summary includes last_thread_summary and last_event_per_type.
Sample chat summary data structure

Form fields

A component of the Form event.
Sample Form fields

Filled form fields

A component of the Filled form event.
Sample Filled form fields

Properties

Properties are key-value storages. They can be set within a chat, a thread, or an event. You can read more about properties in the Configuration API document.
Sample Properties data structure

Threads

Sample Thread data structure

Deleted event

The Deleted Event is returned to agents with the normal role in place of the original event.
Sample Deleted event in response