LiveChat Webhooks and RTM API
Asynchronous event surfaces for LiveChat. HTTP webhooks registered through the Configuration API and the Agent Chat Real-Time Messaging (RTM) WebSocket API share the same event payloads (incoming_chat, incoming_event, chat_user_added, chat_user_removed, customer_updated, agent_*, bot_*, group_*, and more).
LiveChat Webhooks and RTM API is one of 12 APIs that LiveChat publishes on the APIs.io network, described by an AsyncAPI event-driven specification.
Tagged areas include Webhook, Real-Time Messaging, WebSocket, and Event. The published artifact set on APIs.io includes API documentation and an AsyncAPI specification.
Requests are made against the base URL wss://api.livechatinc.com/v3.5/agent/rtm/ws.
Metadata
The identity and technical contract details declared by the specification.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from LiveChat 11
Other APIs LiveChat publishes across the network.
This is an independent, third-party profile of LiveChat Webhooks and RTM API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.