Skip to Content
LYNKORIADocs

Events reference

Realtime socket events delivered to clients, and webhook events delivered to your backend.

Client events (socket)

The client SDK maps socket events to listeners. You rarely need the raw names, but they appear in logs and in the Playground.

Socket eventSDK listenerPayload
message:createdonMessageConversationEvent with type: 'message.created'
message:updatedonMessagetype: 'message.updated' (edit)
message:deletedonMessagetype: 'message.deleted'
reaction:addedonMessagetype: 'reaction.added', with reaction
reaction:removedonMessagetype: 'reaction.removed', with reaction
conversation:readonRead{ conversationId, userId, seq }
conversation:updatedonConversationUpdated{ conversationId, reason }
typing:start / typing:stoponTyping{ conversationId, userId, typing }
presence:changedonPresenceChange, presence.subscribe{ userId, status, lastSeenAt }
call:invited … call:endedonCallStateChangeCall signal sent by your backend
session:expiringHandled by the SDKTriggers a token refresh

A ConversationEvent is { conversationId, seq, type, message, reaction, createdAt }, where message is the message’s current snapshot.

Delivery guarantees

  • Events for one conversation are applied in seq order. Duplicates are ignored, and gaps trigger a fetch from history.
  • After any reconnect, the SDK resyncs every tracked conversation, so missed events are recovered.
  • Typing and presence events are not stored and are not replayed.

Media events

Call media events come from LiveKit on session.room (for example ParticipantConnected, TrackSubscribed, ConnectionStateChanged). Listen with room.on(RoomEvent.…) or use LiveKit React hooks. session.onStateChange reports the simplified connection state.

Webhook events (server)

TypeTrigger
call.startedThe media room started
call.endedThe call ended
participant.joinedA device joined a call
participant.leftA device left or was removed
message.createdA message was stored

Payload fields, signatures and retries are described in webhooks.

On this page