> ## 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.

# HR & Payroll (HRIS)

> The 21 HRIS models, how they are grouped, and which ones accept writes.

Everything under `https://api.bindbee.dev/api/hris/v1/`. Twenty-one models, grouped by what they describe rather than by which endpoint returns them.

Every collection endpoint is paginated and takes the same filters for `ids`, `remote_id` and `modified_after` - see [Pagination](/api-reference/basics/pagination). Every request needs both an API key and a connector token - see [Authentication](/api-reference/basics/authentication).

## The models

| Group                 | Models                                                                                                                                                                                                                                                                                                                | What it answers                                 |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| **Employee**          | [Employee](/hris/employee/get-employees), [Employment](/hris/employments/get-employments), [Compensation](/hris/compensation/get-compensations), [Dependents](/hris/dependents/get-dependents), [Bank Info](/hris/bank-info/get-bank-info-list), [Documents](/hris/documents/get-documents)                           | Who the person is and what is true of them      |
| **Organization**      | [Company](/hris/companies/get-companies), [Group](/hris/groups/get-groups), [Location](/hris/locations/get-locations)                                                                                                                                                                                                 | The structures they sit in                      |
| **Payroll**           | [Payroll Run](/hris/payroll-runs/get-payroll-runs), [Employee Payroll Run](/hris/employee-payroll-runs/get-employee-payroll-runs), [Payroll Run Calendar](/hris/payroll-run-calendar/get-payroll-run-calendars), [Pay Group](/hris/pay-groups/get-pay-groups), [Payroll Codes](/hris/payroll-codes/get-payroll-codes) | What was paid, when, and on what schedule       |
| **Benefits**          | [Employer Benefit](/hris/employer-benefits/get-employer-benefits), [Benefit](/hris/benefits/get-benefits), [Dependent Benefit](/hris/dependent-benefits/get-dependent-benefits), [Benefit Coverage](/hris/benefit-coverages/get-benefit-coverages)                                                                    | What is offered, who enrolled, and for how much |
| **Time & Attendance** | [Time Off](/hris/time-off/get-time-off-list), [Time Off Balance](/hris/time-off-balance/get-time-off-balances-list), [Timesheet Entry](/hris/timesheet-entries/get-timesheet-entries-list)                                                                                                                            | Hours worked and leave taken                    |

<Info>
  The split that catches people most often is **Employee versus Employment**. An employee is a person; an employment is one period of work. One person routinely has several - see [Employee & org models](/guides/data-models/employee-data).
</Info>

## What accepts writes

Four models. Everything else is read-only through the unified API.

| Model                | Endpoint                                  |
| -------------------- | ----------------------------------------- |
| Employee             | `POST /api/hris/v1/employees`             |
| Employee Payroll Run | `POST /api/hris/v1/employee-payroll-runs` |
| Time Off             | `POST /api/hris/v1/time-off`              |
| Timesheet Entry      | `POST /api/hris/v1/timesheet-entry`       |

Each has a Meta endpoint returning the request schema for that connector's integration - build the body from it rather than hardcoding one, since required fields differ per integration. See [Fetch a schema](/guides/reading-writing/writing-data/meta-apis).

There is no update or delete on unified models. Where a correction is possible at all, it goes through [Passthrough](/guides/extending/passthrough).

## Where to start

<CardGroup cols={2}>
  <Card title="Pagination" icon="list" href="/api-reference/basics/pagination">
    Every collection endpoint works this way.
  </Card>

  <Card title="Employee & org models" icon="network" href="/guides/data-models/employee-data">
    How the models relate, and where fields actually live.
  </Card>

  <Card title="Scope & permissions" icon="funnel" href="/get-started/scoping">
    Why a field you expected came back empty.
  </Card>
</CardGroup>