This topic covers essential concepts related to Dyte Live Video applications.
Backend HTTP REST APIs
Your backend utilizes Dyte REST APIs to perform actions such as:
Your applications bundle Dyte Core SDKs (and UI Kits) to acquire, transmit and play media, and manage network connections.
Core SDK: The Dyte Core SDK is designed to provide an easy way to incorporate real-time communication (RTC) solutions. With full customization and branding options, you can build your own UI from the ground up without dealing with complicated media layers. See Introduction to Core SDK.
UI Kit: Dyte's UI Kit is a prebuilt design library of UI components designed to simplify the integration of video and voice calls into your product. See UI Kit.
The Developer Portal serves as a comprehensive platform, offering access to meeting logs, API key management, billing operations, and various other functionalities in one place.
You can also use Developer Portal to create meetings, presets, setup storage for recordings, add webhooks, and much more.
In Dyte, the organization serves as the top-level entity where all participants of your group are added. You can create an organization using the API or through the Developer Portal.
- Meetings are created within the organization.
- The API keys are generated for your organization. These API Keys are unique to your organization and are required to use Dyte REST APIs such as when instantiating a meeting.
- Additionally, Dyte considers the organization as a billing unit.
A communication channel created on Dyte is termed as a
meeting. Meetings can be created using the Create a meeting API or through the Developer Portal. Similarly, you can get the details of your meeting using the API or developer portal.
An example from the Developer Portal displaying meeting details.
In Dyte, a meeting is a communication channel, and each instance of that channel is called a session. A session represents an ongoing meeting within that communication channel. Like meetings, you can get fetch the details of a session via Developer Portal or using the APIs.
An example from the Developer Portal displaying session details.
A preset is a set of permissions and UI configurations that are applied to participants for different meeting types such as Group Call, Webinar, and Livestream. The presets define how a meeting will appear visually and functional aspects of the meeting. They allow customization options like setting maximum number of participants on-screen, permissions to share screen, enabling poll creation, disabling video and audio, adjusting text color, configuring plugins, etc.
For more information, see Add Presets.
Anyone who joins the
meeting, including actual users and machine users. You can add participants using the Add Participant API. Participants will have permissions for the meeting depending on the selected preset. The
presetName must be passed in the body of the Add Participant API request.