Meeting Room Management
This guide will show you how to:
- Retrieve the details for an individual room.
- Get a list of all the rooms associated with your application.
- Change the expiration date for an individual long term room.
Individual Room Retrieval
https://api-eu.vonage.com/v1/meetings/rooms/:room_id
When you create a room, you will get a room id in the response. This id can be used for room retrieval using a
Example Request
This will return a generic Vonage::Response object.
The Vonage::Response object de-serializes the returned JSON data into Vonage::Entity objects, and provides getter methods for the top level properties of that JSON data, for example:
For properties in the JSON data where the value is a JSON object, this is itself de-serialized into a Vonage::Entity object, with its own getter methods. For example, the recording_options getter returns a Vonage::Entity object with auto_record and record_only_owner getters. You can chain these getter method invocations to get to the data you need:
The response will be identical whether the room is long term or instant.
Example Response
Retrieve all Rooms
https://api-eu.vonage.com/v1/meetings/rooms/
To retrieve all rooms, send a
id: Example Request
This will return an object of the Vonage::Meetings::Rooms::ListResponse class.
This class defines an each method, allowing you to iterate through the _embedded array returned in ther response. For example:
The class also includes Enumerable, so you can call any instance method from that module on the object. For example:
Example Response
Expiration Update
PATCH: https://api-eu.vonage.com/v1/meetings/rooms/
The expiration date of a long term room can be updated by using a PATCH action and the room id. The new date should be included in an object called update_details:
Example Request
Please note that only long term rooms can be updated.