Skip to main content

Concepts: Basics

This topic guides you through the standard practices utilized in Twilio Video API and illustrates how they correspond with Dyte's API. The main purpose of this tutorial is to support you in migrating an existing application from Twilio to Dyte's video and audio APIs.


Here's a brief overview of the architecture used by Twilio and Dyte.

For more information on how to get started with Dyte, see Integrate Dyte.


To access Twilio's API, you need an Account SID and Auth Token which can be obtained from Dyte uses Organization ID and API Key that you can get from the Developer Portal.

It's important to note that the credentials for both Twilio and Dyte are intended to be used only on the server-side.

Account SIDOrganization ID
API SecretAPI Key

Rooms / Meeting

Twilio utilizes Rooms to establish connections between participants, whereas Dyte uses Meetings for the same purpose.

Room SIDMeeting ID

Participant Authentication

In Twilio, helper libraries are used to generate a participant access token.

const token = new AccessToken(twilioAccountSid, twilioApiKey, twilioApiSecret, {
identity: identity,

In Dyte, you make a REST API call to Add Participant API which returns authToken.

Access TokenAuthtoken