Quick start
Record a video and play it back, in two pages of HTML. No build step, no framework.
Before you start
You need an api_key, an api_secret and a sandbox organization. Ask us and
you will have them within one working day — the secret is only ever used
server-side, to sign requests.
You also need a recorder id and a player id. Both are configuration objects we create for you; they decide things like branding, retention and which collection videos land in.
1. Record
Place an element, load the recorder, point it at your recorder id.
<!-- Pinned to an exact version. A version path never changes once published. -->
<script src="https://cdn.flipbase.com/recorder/v2.0.0-alpha.2/recorder.js"></script>
<div id="recorder"></div>
<script>
FlipbaseV2.recorder({
selector: 'recorder',
recorderId: 'your-recorder-id',
callback: function (videoId) {
// The only thing you have to keep.
console.log('video UUID:', videoId);
},
});
</script>
The recorder handles camera permission, the viewfinder, retakes and the upload.
When the candidate submits, your callback receives a video UUID as its
first argument. The option is called callback — there is no onSubmit; see
Recorder v2 for its full signature, and
Upload events if you want to follow the
upload as it runs rather than only hear that it finished.
Browsers only grant camera access on a secure origin. Over plain HTTP the camera
is never offered and the recorder falls back to file upload. localhost counts
as secure, so local development is fine.
2. Store the UUID
Save it against whatever record it belongs to — a candidate, an application, a job. That UUID is the whole join between your data and ours.
UPDATE applications SET video_uuid = $1 WHERE id = $2;
3. Play it back
Later, hand the same UUID to the player.
<script
src="https://cdn.flipbase.com/player/v3.0.0/player.min.js"
integrity="sha384-eBPjrM3yXYJtqW6tLbK4bK/Sha7yqVK2/fBgStXvM0fHGzrpXOq6TndocA3rTW6/"
crossorigin="anonymous"
></script>
<div id="player"></div>
<script>
new FlipbasePlayer({
selector: 'player',
video_id: 'the-uuid-you-stored',
player_id: 'your-player-id',
}).mount();
</script>
That is the entire surface area.
What to read next
- Data flow — how the pieces fit, and what we never see.
- Integration patterns — custom element and npm, and when each is the better choice.
- Signatures — the example above plays a
video that needs no signature. Whether one is needed is decided by the
collection's
secure_modeand the video'sprivacy; see Private, published and secure mode. For a candidate's answer you want the signed path. - Browser support — listed on each component's own page, because it is the one thing that differs by version.
A note on versions
Both URLs above pin an exact version — the player's with an integrity hash as well. Keep them that way. A version path never changes once published, so the bytes you test against are the bytes your candidates get.
/player/latest/ exists and moves on its own. It is convenient right up until
the morning it is not. The recorder has no moving alias today: every recorder
path is an exact version, apart from the two frozen unversioned bundles that
predate them — see If your page loads an unversioned
bundle if your page is on one.
Versioned recorder and player paths are served from cdn.flipbase.com only.
app.flipbase.com does not serve them, so do not swap the host.