v1

latestOpenAPI 3.1.1Proprietary2026-07-26184406877.9 KB
Attendance

Fetch attendance summaries

This endpoint returns aggregated attendance summary metrics for one or more employees within a specified date range. Results are returned as a summary per employee per date range and can include total worked hours, payable hours, overtime, breaks, and other attendance metrics (based on the fields you request).

This is a read operation that uses POST because it requires a structured request body (filters, field selection, and pagination parameters). <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 dateRange 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>
post/attendance/summaries/search

Request body

fieldsstring[] required

List of field IDs to include in the response. Standard fields are listed above. Custom fields following the pattern /attendanceSummary/field_<number> are also supported. Required: The array must include /attendanceSummary/employeeId.

limitinteger

Maximum number of items to return per page. Defaults to 100.

cursorstring

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.

includeHumanReadableboolean

This property is not currently supported for this endpoint. Whether to include human-readable formatted values alongside raw values in the response

Example request

{
  "fields": [
    "/attendanceSummary/employeeId",
    "/attendanceSummary/dateRange",
    "/attendanceSummary/hoursWorked",
    "/attendanceSummary/payableHours"
  ],
  "filters": [
    {
      "fieldId": "/attendanceSummary/dateRange",
      "operator": "equals",
      "values": [
        "2025-01-01",
        "2025-01-31"
      ]
    },
    {
      "fieldId": "/attendanceSummary/employeeId",
      "operator": "equals",
      "values": [
        "123456789"
      ]
    }
  ]
}

Response

Attendance summaries matching the search criteria