---
title: "Fetch daily attendance breakdown"
method: POST
path: "/attendance/daily-breakdown/search"
tags: ["Attendance"]
---

# Fetch daily attendance breakdown

`POST /attendance/daily-breakdown/search`

This endpoint allows you to retrieve daily attendance breakdown data for employees. Each item in the response represents one day's attendance data for an employee, including hours worked, breaks, overtime, and other daily metrics. Please note that this endpoint requires body parameters, which is why it utilizes a POST request for a read operation.
<p><b>Before using this endpoint:</b></p> <ul> <li>Explore the <a href="/docs/explore-attendance-api" target="_blank">Attendance API</a> for more details on usage, rate limits, permissions, and more.</li> <li>You must provide both `date` and `employeeId` filters in the request.</li> <li>Only fields mentioned in the `fields` parameter are returned in the response.</li> <li><b>Pagination:</b> Use `limit` and `cursor` parameters to paginate through results. The `cursor` value for the next page is returned in `response_metadata.next_cursor`. To learn more, see <a href="https://apidocs.hibob.com/docs/pagination" target="_blank">Pagination in Bob's API</a>.</li> </ul> <p><b>Testing notes</b>:</p>
  <ul>
  <li>Use the testing widget's <b>Try It!</b> option to test this endpoint.</li>
  <li>Use the <b>Examples > Request Example</b> option to see how to initiate body parameters.</li>
  </ul>

## Request body

- DailyBreakdownSearchRequest — Request schema for searching daily attendance breakdown
  - `fields` string[], required — List of field IDs to include in the response. Standard fields are listed above. Custom fields following the pattern `/dailyBreakdown/field_<number>` are also supported. **Required**: The array must include both `/dailyBreakdown/employeeId` and `/dailyBreakdown/date`.
  - `filters` object[], required — List of filters to apply. You must provide exactly three filters: 1. One `date` filter (fieldId: `/dailyBreakdown/date`, operator: `from`) with exactly 1 start date 2. One `date` filter (fieldId: `/dailyBreakdown/date`, operator: `to`) with exactly 1 end date 3. One `employeeId` filter (fieldId: `/dailyBreakdown/employeeId`, operator: `equals`) with one or more employee IDs
    - `fieldId` '/dailyBreakdown/date' | '/dailyBreakdown/employeeId', required — Field ID for the filter. Use `/dailyBreakdown/date` for date filter or `/dailyBreakdown/employeeId` for employee ID filter.
    - `operator` 'from' | 'to' | 'equals', required — Filter operator. Use `from` or `to` for date filters, `equals` for employee ID filter.
    - `values` string[], required — Filter values. For `date` filter: provide exactly 1 date in ISO format (YYYY-MM-DD). For `employeeId` filter: provide one or more employee IDs.
  - `limit` integer — Maximum number of items to return per page. Defaults to 100.
  - `cursor` string — Opaque cursor for pagination. Use the value from `response_metadata.next_cursor` in the previous response to get the next page. Do not provide in the first request.
  - `includeHumanReadable` boolean — This property is not currently supported for this endpoint. Whether to include human-readable formatted values alongside raw values in the response.

## Response `200`

Daily attendance breakdown matching the search criteria

- DailyBreakdownSearchResponse
  - `items` DailyBreakdownSearchResponseObject[] — Array of daily breakdown objects matching the search criteria
    - `objectType` 'dailyBreakdown' — Type of the object
    - `fields` object — The available daily breakdown fields. Only fields that are specified in the fields filter in the request will be returned.
      - `/dailyBreakdown/employeeId` object — The employee ID
        - `value` string
      - `/dailyBreakdown/date` object — The date this daily breakdown applies to
        - `value` string, date — Date in ISO format (YYYY-MM-DD)
      - `/dailyBreakdown/hoursWorked` object — Hours worked on this day
        - `value` number, double
      - `/dailyBreakdown/potentialHours` object — Potential hours for this day based on attendance policy
        - `value` number, double
      - `/dailyBreakdown/payableHours` object — Payable hours for this day
        - `value` number, double
      - `/dailyBreakdown/regularHours` object — Regular working hours (excluding overtime)
        - `value` number, double
      - `/dailyBreakdown/overtimeHours` object — Overtime hours for this day
        - `value` number, double
      - `/dailyBreakdown/doubleOvertimeHours` object — Double overtime hours for this day
        - `value` number, double
      - `/dailyBreakdown/unpaidBreaks` object — Unpaid break hours deducted on this day
        - `value` number, double
      - `/dailyBreakdown/premiumPayEligibleHours` object — Hours eligible for premium pay on this day
        - `value` number, double
      - `/dailyBreakdown/specialRateEligibleHours` object — Hours eligible for premium pay on days covered by the policy’s special day-of-week rate (for example configured weekends or other off days). If that day is a bank holiday, bank holiday premium rules apply instead.
        - `value` number, double
      - `/dailyBreakdown/totalOvertimeHours` object — Total overtime hours (overtime + double overtime)
        - `value` number, double
      - `/dailyBreakdown/workedRegularHours` object — Regular hours actually worked on this day (excluding overtime)
        - `value` number, double
      - `/dailyBreakdown/isApproved` object — Indicates whether the daily attendance entry is approved, meaning it's included in a timesheet that has been submitted and approved. Note: approval status can change as long as the attendance cycle is not locked. To learn more, see https://apidocs.hibob.com/docs/explore-attendance-api.
        - `value` boolean
  - `response_metadata` object
    - `next_cursor` string, nullable — Opaque cursor for the next page. Provide this value in the `cursor` parameter of the next request to get the next page. When null, there are no more pages.

## Other responses

- `400` — The request is malformed or includes invalid parameters
- `401` — Authentication failed. Check your service user credentials
- `403` — The service user or token is missing the required permissions to access the requested data
- `404` — Feature not enabled for this company
- `429` — Rate limit exceeded - see <a href="https://apidocs.hibob.com/reference/attendance#rate-limiting">Rate limits</a>
- `500` — An unexpected error occurred. Try again or contact support if the issue persists.

---

[API](https://skmtc.net/hibob/apis/employee-data-api.md) · [All operations](https://skmtc.net/hibob/apis/employee-data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hibob/employee-data-api/revisions/0781ebbdda91/schema)