Skip to main content
Pushes are generated primarily by RTM API actions, but also by Web API actions. They notify you when specific events occur and are delivered only over the WebSocket transport. You don’t need to register to receive them. Their Web API equivalents are webhooks. Pushes and webhooks have similar payloads. There are no retries for pushes. General push format

Available pushes


Chats

incoming_chat

Indicates a chat coming with a new thread. The push payload contains the whole chat data structure. If the chat was started with some initial events, the thread object contains them.
Sample push payload

chat_deactivated

Indicates that a chat was deactivated by closing the currently open thread.
Sample push payload

chat_deleted

Indicates that a chat was deleted.
Sample push payload

thread_deleted

Indicates that a thread was deleted.
Sample push payload

threads_deleted

Indicates that several threads from a specific date range or with the same tag were deleted.
Sample push payload

Chat access

chat_access_updated

Indicates an update of a user’s access to a particular chat.
Sample push payload

chat_transferred

Indicates that a chat was transferred to a different group or to an agent.
Sample push payload

Chat users

user_added_to_chat

Indicates that a user (customer or agent) was added to a chat.
Sample push payload

user_removed_from_chat

Indicates that a user (customer or agent) was removed from a chat.
Sample push payload

Events

incoming_event

Indicates an incoming event sent to a chat.
Sample push payload

event_updated

Indicates that an event was updated.
Sample push payload

incoming_rich_message_postback

Indicates an incoming rich message postback. The push payload contains the info on the postback itself, as well as the chat it was sent in.
Sample push payload

Properties

chat_properties_updated

Indicates which chat properties were updated.
Sample push payload

chat_properties_deleted

Indicates which chat properties were deleted.
Sample push payload

thread_properties_updated

Indicates which thread properties were updated.
Sample push payload

thread_properties_deleted

Indicates which thread properties were deleted.
Sample push payload

event_properties_updated

Indicates which event properties were updated.
Sample push payload

event_properties_deleted

Indicates which event properties were deleted.
Sample push payload

Thread tags

thread_tagged

Indicates that a chat thread was tagged.
Sample push payload

thread_untagged

Indicates that a chat thread was untagged.
Sample push payload

Customers

incoming_customers

Indicates customers the agent should be aware of. Sent after login.
Sample push payload

incoming_customer

Indicates that a new or returning customer is available to the agent. Sent when:
  • a new customer registers
  • a customer who previously left the tracked website returns
  • a followed customer who was temporarily unavailable becomes available again (e.g., after being transferred between groups)
Sample push payload

customer_updated

Indicates that customer data changed. The push payload contains the updated fields.
Sample push payload

customer_page_updated

Indicates that a customer moved to another page of the website.
Sample push payload

customer_banned

Indicates that a customer was banned for a specified number of days.
Sample push payload

customer_transferred

Indicates that a customer is no longer available to the agent.
Sample push payload

customer_left

Indicates that a customer left the tracked website.
Sample push payload

Status

routing_status_set

Indicates that an agent’s or bot agent’s status was changed.
Sample push payload

agent_disconnected

Indicates that an agent was disconnected. The payload contains the reason for the disconnection.
Sample push payload

Configuration

agent_created

Indicates that a new agent account was created. The payload contains the full state of the agent data structure, including empty fields.
Sample push payload

agent_approved

Indicates that an agent’s account was approved and is now active.
Sample push payload

agent_updated

Indicates that an agent’s configuration changed. Contains only the updated properties.
Sample push payload

agent_suspended

Indicates that an agent’s account was suspended.
Sample push payload

agent_unsuspended

Indicates that an agent’s account was unsuspended.
Sample push payload

agent_deleted

Indicates that an agent’s account was deleted.
Sample push payload

auto_accesses_updated

Indicates that auto access rules were modified. The payload contains an array of all changes resulting from adding, updating, or deleting an auto access rule.
  • For an added auto access rule: the payload contains the complete state of the rule data structure, including empty fields.
  • For an updated auto access rule: the payload contains only the updated properties.
  • For a deleted auto access rule: the payload confirms the deletion.
Sample push payload (rule added)
Sample push payload (rule updated)
Sample push payload (rule deleted)

bot_created

Indicates that a new bot was added. The payload contains the full state of the bot data structure, including empty fields.
Sample push payload

bot_updated

Indicates that a bot’s configuration changed. Contains only the updated properties.
Sample push payload

bot_deleted

Indicates that a bot was deleted.
Sample push payload

group_created

Indicates that a group was created within a license. The payload contains the full state of the group data structure, including empty fields.
Sample push payload

group_deleted

Indicates that a group was deleted within a license.
Sample push payload

group_updated

Indicates that a group was updated within a license. The push payload only includes the updated fields.
Sample push payload

tag_created

Indicates that a tag was created within a license. The payload contains the full state of the tag data structure, including empty fields.
Sample push payload

tag_deleted

Indicates that a tag was deleted within a license.
Sample push payload

tag_updated

Indicates that a tag was updated within a license.
Sample push payload

groups_status_updated

Indicates that the statuses of groups the agent has access to were updated. The push payload only includes the updated fields. Possible statuses: accepting_chats, not_accepting_chats, offline.
Sample push payload

Other

events_marked_as_seen

Indicates that a user has seen events up to a specific time.
Sample push payload

incoming_sneak_peek

Indicates the message a customer is currently typing.
Sample push payload

incoming_typing_indicator

Indicates that one of the chat users (an agent or a bot agent) is currently typing a message. The message hasn’t been sent yet.
Sample push payload

incoming_multicast

Indicates messages sent via the multicast method or by the system.
Sample push payload

chat_unfollowed

Indicates that a chat has been unfollowed. Useful in multiple connection scenarios, where one app or integration needs to know that another unfollowed the chat.
Sample push payload

queue_positions_updated

New positions and wait times for queued chats.
Sample push payload