Gruveo Embed API as well as the mobile SDKs allow you to record the users’ calls, with the composite call recordings uploaded straight into your own Amazon S3 bucket or an FTP/SFTP server. This page explains the necessary prerequisites, recording file properties as well as other important information regarding call recordings.
In order for us to setup call recording for your API account, we will need your client ID (request one here) as well as the following information.
Please see here for a tutorial on creating an IAM user with permissions to access a single S3 bucket.
Once you have the above information ready, please contact us to have call recording set up for your API account.
Once a call has been established, toggling call recording is as simple as calling the corresponding method in the API or the mobile SDK. For example, here is how to start and stop call recording with the Gruveo Embed API:
// Start call recording.
// Stop call recording.
Starting and stopping call recording are asynchronous processes. The Embed API and mobile SDKs notify you of any changes to the current call’s recording state via corresponding events, e.g. the
recordingStateChange event in the Embed API.
All call recordings are made in HD (1280×720) with the H.264 codec for video and AAC for audio. Recording files are composited, meaning that the pictures of the participants are combined, with dynamic maximization of the active speaker’s picture.
You are welcome to check out the recording functionality using the demo API credentials:
When using these demo credentials, all call recordings are uploaded to the publicly accessible
gruveo-api-demo-recordings S3 bucket:
Check out the Embed API demo for an example of using the call recording functionality.