Twilio migration - What is what?

I’m migrating my app from Twilio to Zoom. I feel completely lost. Here is the setup of my application with Twilio:

  • I have a backend that has REST endpoints for returning token to participants, creating meeting rooms, starting meeting rooms, closing meeting rooms
  • I also use the call recordings and need access to the location of the recordings in order to so some post-processing on them. For this I use the Twilio APIs.
  • I have built the web frontend of the video call (i assume this is the simplest step for migration)

My question is, what are the equivalents of each of these endpoints in Zoom world? I so far have managed to understand how to create JWT tokens for participants. But I can’t understand how everything else work. Does the backend need to create meeting rooms for participants prior to their meeting?

Hi @r.asgari.g ,

I’m glad you are migrating! Have you checked out our migration guide for Web?

With Zoom and the Video SDK, sessions are created when the first user joins the session. Unfortunately, there is not a way currently to create a session via REST API, however, Zoom handles it automatically for you. We do have REST APIs for other session related use cases that I suggest you learn about here. Is there a reason you must start the session via REST API?

You can access cloud recording both via REST API and Webhook. I’d recommend using the cloud_recording_completed webhook to automatically perform whatever you are looking to do when the session has ended and the recording is ready.

Best,
Will

1 Like

Thank you for the reply. The reason I handled all creation of meetings and state changes on backend was because I wanted to link meetings and recordings (and eventually the processed information extracted from recordings) in my database.

I see that there is a session_id in the REST API docs you shared. How do I get this when users enter the meeting?

1 Like

Hi @r.asgari.g ,

You can simply call client.getSessionInfo() on Web to get the session info, which contains the session id. Documentation here.

The session.recording_completed webhook also includes the session id of the session in which the recording was made. I would look into this documentation.

Best,
Will

2 Likes