Step 1: Configure the Application Key Scheduled Session

        This will configure all the Rooms tied to the Application Key as Persistent.

Step 2: Create scheduled sessions for specific rooms

You can create a scheduled session by doing a REST call by POST to the Meeting Resources API. (See Create Meeting Resources API doc)

On your application's UI, this will generally refer to to creating a scheduled video/audio call meeting. 

Step 3: Retrieve scheduled sessions

You can retrieve the all the created scheduled sessions by doing a REST call by GET to the Meeting Resources API.

There are two types of REST calls. GET /rest/meetings/:appid/:room allows you to retrieve scheduled sessions for a specific room while GET /rest/meetings/:appid/ allows you to retrieve scheduled sessions for all rooms under an Application Key.

On your application's UI, this will generally be used to obtain and display a list of scheduled video/audio call meetings as calendar or list.

Step 4: Delete scheduled sessions (optional)

You can delete created schedules session by doing a REST call by DELETE to the Meeting Resources API.

(See our API doc: DELETE /rest/meetings/:mid)

On your application's UI, this will generally be used to a cancel (or delete) the meeting item.

Step 5: Starting the scheduled session call

You can start the scheduled Room session by authenticating the connection via credentials format as detailed in our Authentication Guide.

You will need to provide the duration, startDateTime stamp and the generated credentials based off the Application Key secret, duration and startDateTime stamp.