Developer docs
Integration patterns
Three shapes of integration: ATS-native partner activation, embedded application form, custom backend.
There are three integration patterns. Pick the one that matches what you are building. They are not exclusive, you can mix them in the same organization.
Pattern 1, ATS-native (1-click activation)
If you run one of the eight ATSes Flipbase ships with pre-built (Varbi, Cornerstone, Bullhorn, Ubeeo, Recruitnow, Talentech, CVWarehouse, The Solutions Factory), there is no integration work. Flipbase enables your account on the ATS partner's side, you authorise the connection on yours, and the recorder + player surface inside the ATS automatically.
In this pattern, your developers don't touch recorder.js or player.js directly. The ATS partner has already integrated them, and Flipbase provisions your account's recorderId and player_id inside that integration. You configure the question text and the role-level settings from your ATS admin UI.
Pattern 2, embedded application form
If you host your own careers page or application form (Webflow, Wordpress, custom React, anything), embed recorder.js directly into the form. The video UUID arrives in your callback, you submit it as part of the form payload to your own backend, you store it against the application record.
This is the most common shape outside ATS-native integrations. It works on any web stack because it is two script tags and two divs.
Pattern 3, custom backend
If you are doing something the form-based shape does not cover (asynchronous follow-up videos triggered from an internal tool, scheduled video prompts driven by a CRM event, multi-stage interview flows with branching), call the Flipbase API directly from your backend.
Create a video record server-side, return its identifier to the candidate-facing surface (typically via email), and let the candidate complete it asynchronously. The recorder.js library still does the capture, but your backend owns the orchestration.
Custom backends call the API directly. See the full reference on Postman.
Open the API reference →Which to pick
| You are | Pattern |
|---|---|
| On a supported ATS, you want the fastest activation | ATS-native (1-click) |
| Hosting your own careers page or applicant form | Embedded application form |
| Running a custom recruitment flow, internal tool, or branching interview | Custom backend |
| On an unsupported ATS but with an extension point or webhook | Custom backend or embedded form, depending on the extension |
Ready to call the API?
The full reference is on Postman. To actually call it you need an api_key + api_secret + sandbox organization. Reply within one working day.