2. RingCentral provides various service and feature in the space of cloud
communication. Call recordings is an important part of every voice
communications service and RingCentral provides this service from
RingCentral ’s mobile, desktop and web applications.
3. The Call recordings capability of RingCentral provides the availability of
call recordings for retrieval and streaming playback via the API which
easily enhance the all capabilities provided by RingCentral. For
example, analyzing recording voice communications to enhance
customer interactions, responding to inquiries etc are some of the
examples of it's use cases.
4. RingCentral provides Call recordings APIs which can be found here (in
API explorer) and it support streaming playback as using HTML5 audio
which means It is possible to playback a RingCentral call recording with
using an HTML5 audio element without downloading and hosting the
audio file. Call recordings can be in MP3 or WAV format.
We can Embed Call Recordings in a Web Page and can use HTML5
supported browsers and the <audio> tag in a web page.
5. The Call recordings APIs uses call log API for query to retrieve
information on calls with recordings. If you see the APIs below:
/restapi/v1.0/account/accountId/recording/recordingId
The API returns call recordings by ID(s)
The app permission required is ReadCallRecording
6. The APIs are protected by RingCentral OAuth services that authenticate
the users with login and single sign on facilities specially in the case of
3rd party which uses these RingCentral APIs.
7. We can also call the Recording API endpoint and retrieve the media
directly by creating following format manually :
https://media.ringcentral.com/restapi/v1.0/account/{account-
Id}/recording/{recording-Id}/content
This url we will generally get from the response of Get User Call Record
API in contentUri section as hypermedia links.
8. RingCentral provides APIs for simple and detailed call log records from
API calls. While the call is ongoing, the recording will not be available
for retrieval, even if the recording id is present in the Call Session
Notification event. There is usually a delay of 30 seconds for completed
calls before we try to retrieve the call logs using the GET request.