Event

Something that happened. Sent to your app as a callback, or to your backend as a webhook.

An event tells you something happened, like a user joining or a message arriving. Events are how your code reacts to what's going on in a call, a chat, or a stream.

Livqeno sends events in two separate ways, to two different places. Choosing the right one is one of the first design decisions in a Livqeno app.

Something happense.g. alice sends a message

Client eventReaches your app instantly, only while it is connected.

Webhook eventReaches your backend as an HTTP POST, even if no app is open.

One thing happens; two kinds of event report it.

1. Client events (in your app)

These fire inside your app, from the SDK you're using. They only arrive while the app is connected. Use them to update the screen.

In your browser app:

room.on('participantJoined', (participant) => { /* ... */ });
chat.on('message', (message) => { /* ... */ });

17 room events and 15 chat events, all typed.
Full lists: RTC events and Chat events.

2. Webhook events (to your backend)

These go from Livqeno's servers to a URL on your backend. Use them for work that must happen even when no app is open: saving data, sending notifications, starting jobs.

17 event types today: chat messages, reactions, chat conversations and their members, and the live-stream lifecycle. Video calls send none.
Full list: Event catalogue.
How to receive them: Webhook.

Which one should I use?

You want to…	Use
Show a new message on screen	Client event
Show who just joined the call	Client event
Save a message in your own database	Webhook
Send a push notification to a user who isn't connected	Webhook
Start a job when a stream ends	Webhook

Simple rule: if it should stop when the tab closes, use a client event. If it must happen no matter what, use a webhook. Many apps use both for the same thing: a client event to show a message, and a webhook to save it.

The two lists are different

An event on one side doesn't always exist on the other.

RTC track changes and connection-state changes are client only. There are no webhooks for them.
The webhooks room.created, participant.joined, and participant.left come from chat conversation membership, not from RTC rooms.

Next steps

Webhook: receive backend events safely.
RTC events · Chat events · Stream events
Event catalogue: all three in one table.