Skip to main content


Basic Concepts

This section takes you through Dyte's key concepts and the terminology.


In Dyte, the organization serves as the top-level entity where all participants of your group are added. You can create an organization through the Developer Portal or using the API

  • 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 or a meeting that happened. Like meetings, you can get fetch the details of a session via Developer Portal or using the APIs. After a minute of all participants leaving, the session is ended and any participants that join after that will result in the creation of a new session.

An example from the Developer Portal displaying session details.


Preset 🚨

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.

To create a preset, please refer to our Developer Portal's Presets Section.



Now that you are familiar with the terminology of basic concepts on Dyte, we can take a look at how different parts of the Dyte system come together. The components are the REST API, core SDK , UIKit and a Developer Portal. Each of these serve different purposes and belong in different blocks of your application.

Let's dive deeper into what purpose each of these components server.

Developer Portal

To begin with, let's start with our dashboard. This is where you will do a number of administrative tasks. This is your go-to-place for things like defining organisations, meeting logs, grabbing API Keys and billing operations. You can also use Developer Portal to create meetings, presets, setup storage for recordings, add webhooks, and much more.



The REST APIs help your server orchestrate the meetings, the participants in them, the recordings etc. You can also observe your meetings and all the associated data with them.

Core SDK

The Core SDK provides all the client side business logic, handles media and networking and provides easy to use APIs to let you program the experience.

Initializing the Core SDK requires an authToken which is unique to every participant in a meeting. The authTokenis returned from the Add Participant API. The Core SDK itself does not provide any UI components and is a data-only API.

UI Kit

We provide a library of UI components that makes it easy to integrate video and voice calls into any app or website within minutes. You can either use it as a prebuilt setup where a single component provides you the entire functionality or you can mix and match - use some components from our library and build some of them on your own.