Skip to main content

v1.1.2

· 3 min read
John Renfrew
John Renfrew
Programmer and data architect

Version 1.1.2 internal test release​

  • Echo360 API
  • Updated SurveyJS to 2.5.13
  • more

Echo360 has an API, which allows us to manage User accounts (and media). We have tested the API, and have scripts running in FileMaker to query Student users, based on Moorlands Email address. There is also a script to create a user, and Echo then sends them an email invite to the platform. We need to investigate what happens with the MCEE students and time zones on sign-up.

The access token for the API is valid for 1 hour, after which the refresh token can be used to retrieve another, along with a new refresh token. Each refresh token may only be used once, so it there is some failure, the process needs to use the client-credentials workflow as a fallback.

The creation of the Echo360 account could be scripted as part of the initial student comms from Technical Support. With API access, the User accounts could then be removed as part of the end-of year or leaving process.

Echo360 Video​

It may be that using the User account to hook to any video uploads is not the right thing to do, as the Student:

  • would have to manually create a sharing link so that it can be pasted
  • has the opportunity to delete the file after upload

Next investigations will cover the mechanics of uploads through the DigiFolio, but sent to a holding account, which ensures that students can not see anyone else's work (but also their own)

The Core Problem​

The Echo360 public API (/public/api/v1/medias) does not expose raw file download URLs for media. The /medias endpoint returns metadata about media items (title, ID, duration, owner, status, etc.), but there is no field in the response that gives you a direct link to the underlying MP4 file. Echo360's architecture deliberately abstracts away the raw files — they're stored in S3 behind authenticated, signed URLs that are generated on-the-fly by the player, not exposed through the public API.

There are plenty of alternatives for S3 compatible storage, which could provide a signed (time-limited) download link, but the better option might be through a site that offers a stremaing viewer, which also implies a need for encoding. Alternative to investigate is BunnyStream. The pricing for this is micropriced, based on storage volume and playback traffic, so needs some research into the projected volumes.

SurveyJS​

We have also updated SurveyJS to the latest version, 2.5.13, which includes some bug fixes and performance improvements. We have tested the new version with our existing surveys, and everything seems to be working fine.
We have also made some minor revisions and corrections to our documentation specifications and codebase, which should improve the overall stability and usability of the system.