How does Robin Messaging work?
How Robin for Messaging Works
Robin for Messaging leverages the good old WebSocket Communication Protocol — Robin acts as an extra layer to ensure persistent and reliable connections across communication channels.
For every Robin App created, the API Key for that app grants you access to the Robin connection, the WebSocket connection. When this connection is opened, Robin sends messages and events that are triggered by the activity of other users of your Robin App (users that have integrated Robin with your API key). However, this depends on the channel the said users subscribe to.
Channels on Robin are characterized by each Robin App, and they are built to ensure that messages are locked in, not leaked, and not susceptible to message interception by other developers or users in the same Robin App.
Channels can be considered as tunnels that relay and retrieve messages to all connected clients.
Robin also supports modern messaging features — like message reactions, voice recording, online presence, and group and direct conversations from an API level to SDK/UI Kits level.
The Robin App
At the heart of every Robin API Integration is a Robin App; it is the smallest unit that contains all components to function independently and power interactions. Upon creating a Robin account, every user is prompted to create a Robin App. A Robin App is the parent channel of every interaction by all users subscribed to it using the API Key.
Check out Robin Fundamentals, for a brief description of the necessary components that make up every Robin Integration.
Last updated
