This documentation is meant for implementation partners who want to use the recorder, player or both.
The documentation should you guide through some basic concepts of our service and how you can use the different parts of the Flipbase service. The documentation assumes knowledge of programming and networking.
If you want to use Flipbase you can choose multiple paths to implement Flipbase:
You implement the recorder and player application, but do not implement any communication with our API. Flibpase will provide you with a recorder_id and player_id (for each customer). This implementation path is usually sufficient if you only need to implement Flipbase for a single (or very few) customers.
You create a client that will communicate with the Flipbase API's, so you can create your own player_id's and recorder_id's. This implementation is usually advised for recruitment software providers (like Application Tracking Systems, Onboarding software providers and Job sites).