---
title: "Payslips"
method: GET
path: "/hris/payslips"
tags: ["Unified HRIS API"]
---

# Payslips

`GET /hris/payslips`

Retrieve all payslips for all employees, across all time.

A payslip is the individual pay statement an employee receives for one pay run, detailing what they were paid. Each payslip embeds the `employee` it belongs to and the `pay_run` it was paid out through, its `totals`, and the `line_items` that make it up (earnings, deductions, and contributions). Filter by `employee_ids`, `payrun_ids`, or `legal_entity_ids` to narrow the results.

Top level filters use AND, while individual filters use OR if they accept multiple arguments. That means filters will be resolved like this: `(id IN ids) AND (remote_id IN remote_ids)`

## Query parameters

- `cursor` string — An optional cursor string used for pagination. This can be retrieved from the `next` property of the previous page response.
- `page_size` integer — The number of results to return per page. Maximum is 250.
- `updated_after` string, date-time — Filter the entries based on the modification date in format `YYYY-MM-DDTHH:mm:ss.sssZ`. Returns records where either the record itself **OR** its nested data has been updated since this timestamp, even if the record's own `changed_at` field remains unchanged. If you want to track entry deletion, also set the `include_deleted=true` query parameter, because otherwise, deleted entries will be hidden. For more details, see [Understanding changed_at vs updated_after Behavior](https://docs.kombo.dev/ats/getting-started/fetching-data#understanding-changed_at-vs-updated_after-behavior). For this endpoint, `updated_after` matches when the returned record changed, or when related data changed as described below. | Path | Added/Removed | Linked Record | | --- | --- | --- | | `employee` | ✗ No | ✗ No | | `pay_run` | ✗ No | ✗ No | | `line_items` | ✓ Yes | ✓ Yes | | `line_items` → `salary_type` | ✗ No | ✗ No | _**Added/Removed**: Whether adding or removing entries from this list triggers an update (n/a for single records). **Linked Record**: Whether changes to the linked record itself trigger an update._
- `include_deleted` 'true' | 'false' — By default, deleted entries are not returned. Use the `include_deleted` query param to include deleted entries too.
- `ignore_unsupported_filters` 'true' | 'false' — When set to `true`, filters targeting fields not supported by this integration will be ignored instead of filtering out all results.
- `ids` string — Filter by a comma-separated list of IDs such as `222k7eCGyUdgt2JWZDNnkDs3,B5DVmypWENfU6eMe6gYDyJG3`.
- `remote_ids` string — Filter by a comma-separated list of remote IDs.
- `legal_entity_ids` string — Filter by a comma-separated list of legal entity IDs.
- `employee_ids` string — Filter by a comma-separated list of employee IDs.
- `payrun_ids` string — Filter by a comma-separated list of payrun IDs.

## Headers

- `X-Integration-Id` string, required

## Response `200`

GET /hris/payslips Positive response

- GetHrisPayslipsPositiveResponse
  - `status` 'success', required
  - `data` object, required
    - `next` string, nullable, required — Cursor string that can be passed to the `cursor` query parameter to get the next page. If this is `null`, then there are no more pages.
    - `results` object[], required
      - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
      - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
      - `changed_at` string, date-time, required — The timestamp when this specific record was last modified. This field only updates when properties directly on this record change, NOT when related or nested models change. For filtering that considers nested data changes, use the `updated_after` parameter which will return records when either the record itself OR its related models have been updated.
      - `remote_deleted_at` string, date-time, nullable, required — The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.
      - `remote_data` object, nullable, required — Includes the data fetched from the remote system. Please be aware that including this in you scope config might violate other scopes that are set. Remote data always has the endpoint path that we got the data from as the top level key. For example, it could look like: `{ "/companies": { ... }}` This is not available on all plans. Reach out to Kombo if you need it.
      - `totals` object, required
        - `gross_pay` object, nullable — The total gross pay for the payslip, before taxes and after gross deductions.
          - `currency` string, required — The [ISO 4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) the value is denominated in.
          - `value` number, double, required — The monetary value.
        - `net_pay` object, nullable — The total net pay for the payslip, after taxes have been applied to the gross pay.
          - `currency` string, required — The [ISO 4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) the value is denominated in.
          - `value` number, double, required — The monetary value.
        - `paid_amount` object, nullable — The amount of the payslip that was actually paid out to the employee. This value accounts for net earnings and deductions.
          - `currency` string, required — The [ISO 4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) the value is denominated in.
          - `value` number, double, required — The monetary value.
      - `employee` object, required — The employee that the payslip is for.
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `first_name` string, nullable, required — The employee’s first name.
        - `last_name` string, nullable, required — The employee’s last name.
        - `display_full_name` string, nullable, required — The employee’s full name, including any middle names. Not all HR systems provide an explicit display name, so we recommend falling back to `first_name` and `last_name`.
        - `work_email` string, nullable — The employee’s work email address. If the email address is invalid, we will set this to `null`.
        - `remote_deleted_at` string, date-time, nullable, required — The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.
      - `pay_run` object, nullable, required — The pay run the payslip was paid out through.
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `start_date` string, date, nullable, required — The start date of the pay run, as a calendar date (`yyyy-MM-dd`).
        - `end_date` string, date, nullable, required — The end date of the pay run, as a calendar date (`yyyy-MM-dd`).
        - `legal_entity_id` string, nullable, required — The Kombo ID of the pay run’s legal entity. The ID can be used to retrieve the legal entity from the `get legal entities` endpoint.
      - `line_items` object[], required — The individual earnings, deductions, and contributions that make up the payslip.
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. For some integrations, this ID can still change if the payslip is edited.
        - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key. This value may include the item's position on the payslip, which can change if the payslip is edited.
        - `name` string, nullable, required — The name of the salary type.
        - `amount` object, nullable — The amount of the line item.
          - `currency` string, required — The [ISO 4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) the value is denominated in.
          - `value` number, double, required — The monetary value.

## Other responses

- `default` — The standard error response with the error codes for the HRIS use case.

## Changes

- **2026-08-27** `7fa930b39366` — 20 breaking, 1 warning, 13 info
  - the response property `data/results/items/line_items/items/amount` became nullable for the status `200`
  - the response property `data/results/items/line_items/items/name` became nullable for the status `200`
  - the response property `data/results/items/pay_run` became nullable for the status `200`
  - the response property `data/results/items/pay_run/end_date` became nullable for the status `200`
  - …30 more

[Change history](https://skmtc.dev/kombo/apis/kombo-api/changes/hris/payslips/get.md)

---

[API](https://skmtc.dev/kombo/apis/kombo-api.md) · [All operations](https://skmtc.dev/kombo/apis/kombo-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kombo/kombo-api/revisions/7fa930b39366/schema)