The building blocks of your Robin Integration.
Robin provides developers with numerous APIs and SDKs across different programming languages and frameworks — each with a different setup, although many of these APIs have a few similar prerequisites before they can be fully set up and integrated.
We call these prerequisites the fundamental parts of Robin as they are the building blocks of any Robin Integration.
There are no integrations without a Robin Account; an account allows access to the Dashboard. The Robin Dashboard is a control centre for all of Robin’s services; you can access your API keys and secret keys, among others. If you do not yet have an API key, you can start by Setting up your Robin account
An API key is a unique string used to recognize requests to your Robin App when you integrate the Robin API.
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. Every user is prompted to create a Robin App upon creating a Robin account.
A critical component of every messaging infrastructure is a sender and a recipient. Whether it is a direct conversation (one-on-one) or a group conversation, users always need to send messages to one another; Robin uses the RUT to identify these users.
Robin keys are different from API Keys. While RUTs help Robin to identify every user in a Robin App, Robin Keys are used to extract other fields that are mapped to users in your Robin App. Some of these fields are
Still not getting it? Check out The What and Why: Robin Keys to fully grasp the concept of Robin Keys.
All messages and Robin Messaging Events sent via Robin are sent through channels. Channels can be considered as tunnels that relay and retrieve messages to all connected clients. For more on how Robin uses channels, see How does Robin Messaging work?
With knowledge of the fundamentals above, you are ready to integrate the Robin API and SDKs in any product of your choice with no hitches.