Skip to main content
Your customers keep their employee data in whichever system they already bought - BambooHR, ADP, Workday, Paycom, or a smaller payroll provider. Your product needs the same employee record out of all of them. Bindbee sits between those systems and yours. You integrate once, against one API and one data model. Whichever system a customer connects, their data is normalized to a single schema before it reaches your code.

​
Bindbee features

One API, three categories

HRIS, ATS, LMS - whether an employee record comes from Workday or as a File, it reaches you with the same fields and types.

Nothing is hidden

The full upstream payload stays available as raw_data. Whatever the unified model doesn’t carry, you can map as a custom field.

Self-serve Setup

Your customers authorize through a magic link or an Embedded SDK in your product.

Write back capability

Create an employee or push a deduction through the same API.

​
Reading and writing data

Most integrations start by reading: Bindbee pulls from the source system, normalizes it, and serves it through the unified API. See Reading data. Bindbee writes back too, through the same API and the same models. See Writing data, or Reading & Writing Data for how the two fit together.
Your customer’s system stays the system of record. Bindbee reads from it and writes back to it; it doesn’t replace it, and it doesn’t run payroll.

​
Where to next

Quickstart

Prerequisites and the fastest path to your first API response.

Platform Overview

A tour of the Dashboard - connectors, logs, scoping and webhooks, and where each lives.

Core concepts

Environments, scoping, connector and connection - the terms the docs use with a specific meaning.

API reference

Endpoints, parameters and schemas.