> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bindbee.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Bindbee?

> Integrate once and reach every HR system your customers already use.

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

<CardGroup cols={2}>
  <Card title="One API, three categories" icon="git-fork" href="/get-started/integrations">
    `HRIS, ATS, LMS` - whether an employee record comes from Workday or as a [`File`](/get-started/connection-methods), it reaches you with the same fields and types.
  </Card>

  <Card title="Nothing is hidden" icon="eye-off" href="/guides/reading-writing/raw-data">
    The full upstream payload stays available as `raw_data`.
    Whatever the unified model doesn't carry, you can map as a [`custom field`](/guides/extending/custom-fields).
  </Card>

  <Card title="Self-serve Setup" icon="unplug" href="/get-started/how-to-connect">
    Your customers authorize through a `magic link` or an
    [`Embedded SDK`](/guides/sdk/embedded-sdk) in your product.
  </Card>

  <Card title="Write back capability" icon="pencil" href="/guides/reading-writing/writing-data">
    Create an employee or push a deduction through the same API.
  </Card>
</CardGroup>

## 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](/guides/reading-writing/reading-data).

Bindbee writes back too, through the same API and the same models. See [Writing data](/guides/reading-writing/writing-data), or [Reading & Writing Data](/guides/reading-writing/overview) for how the two fit together.

<Note>
  **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.
</Note>

## Where to next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/get-started/quickstart">
    Prerequisites and the fastest path to your first API response.
  </Card>

  <Card title="Platform Overview" icon="layout-dashboard" href="/get-started/platform">
    A tour of the Dashboard - connectors, logs, scoping and webhooks, and where each lives.
  </Card>

  <Card title="Core concepts" icon="lightbulb" href="/get-started/core-concepts">
    Environments, scoping, connector and connection - the terms the docs use with a specific meaning.
  </Card>

  <Card title="API reference" icon="terminal" href="/api-reference/basics/authentication">
    Endpoints, parameters and schemas.
  </Card>
</CardGroup>
