Overview

Flipbase ships two browser components and an API. Drop the recorder into your candidate-facing flow to capture a short video answer. Store the video UUID returned by the recorder against the candidate record in your system. Use the player later to play it back. That is the entire surface area.

The components

The recorder is a JavaScript library that mounts into a div on your page. It handles camera permission, a 16:9 viewfinder, a record button, file upload as a fallback, multi-take logic, and the upload of the recorded video to Flipbase storage. When the user submits, a callback fires with a UUID.

The player is a separate JavaScript library that mounts into a div on your page. It reads a video UUID, fetches the video record from the API, and renders an HTML5 video player against it. Two URLs, two scripts, one shared data model.

What it looks like

Final step · Record your answer

Back

Tell us in sixty seconds, why this role?

Senior brand designer · Acme Studio· You'll preview before sending.

Camera ready

0:00 / 1:00

Switch cameraMic & quality

Upload·Audio only·Test mic

The recorder above is a static mockup of the candidate-facing UI. The live recorder behaves the same way, with a live camera preview instead of a placeholder image.

Where things live

• Concepts (data flow, integration patterns, security) for understanding how a video moment moves through your stack.
• Components (recorder, player) for embedding either library, with parameter tables and code snippets.
• Reference (API reference, browser support) for the full API on Postman and the supported platform matrix.

Everything in these docs is public. The only thing that requires a request is API credentials (api_key, api_secret, sandbox organization), issued per partner.

Where to start

• If you are scoping an integration: read Integration patterns and Data flow next.
• If you are evaluating fit: read Recorder, Player, and Security.
• If you are doing a procurement review: read Security and Browser support.