Shortly after a session has ended (and if the relevant recording options were enabled for it), a recording will be available so that students can review the lesson. Recordings can be disabled on an organisation level under the Organisation Settings of your dashboard.
Recordings can be accessed either via the Lessonspace dashboard or via API calls.
In Lessonspace, a recording is not just a video of the previous session. Instead, a link is provided where you are taken to the Space as a playback user. A recording is a series of captured events synced up with recorded AV. You can download images and resources, move freely within the Space, and even switch to different users' perspectives.
If your users have access to the Lessonspace dashboard, they can access recordings for a session from the Sessions page. By default, access is controlled using the relevant recording access policy that you have defined, such as Participant, Student, or Admin.
In the context of the Lessonspace API, the terms "playback URL" and "recording URL" mean different things, but have similar names for historical reasons.
A playback URL points to the Lessonspace API (eg. https://api.thelessonspace.com/...) and is not itself a link to a recording, but merely returns a link to a recording when called via HTTP GET. Playback URLs must be authenticated with an API key when called.
A recording URL is the URL returned by calling a playback URL successfully. A recording URL points directly to a recording itself and is hosted on room.sh (eg. https://go.room.sh/...). This link is by default not authenticated: anyone that has this URL can access it and view the recording for up to 3 hours from time of generation. If you wish this link to also be authenticated, you will need to pass additional values when calling the playback URL.
To get a recording for a specific session, call the dedicated playback endpoint with your API key. This endpoint returns a JSON structure that contains a recording_url property that can be used directly.
Several other endpoints, such as the Organisation Session List endpoint, include a playback_url property for each session. This URL points to the same dedicated endpoint mentioned above, simply with the necessary parameters pre-filled for convenience. Those URLs must still be called with an API key.
Playback URLs that end with /redirect/ are legacy endpoints. These are no longer supported.
Recordings support being embedded in an iframe much like Spaces.
Be sure to set the allow attribute so that all features of the Space work correctly. You can copy and paste the snippet below and replace the src of the iframe tag with the relevant recording URL.
<iframe
src="RECORDING_URL_GOES_HERE"
allow="camera; microphone; display-capture; fullscreen;"
frameborder="0">
</iframe>