The Attendance API now supports a new entry type parameter: ‘work’ or ‘break’.

You can now import manual 'break' entries through the Attendance API. Manual breaks allow employees to record their breaks manually, which is done in the app by clicking the coffee cup icon.

Manual breaks are supported only when imported in "immediate" mode and require a policy that allows manual breaks.

To learn more, see Import attendance data.

The GET endpoints for time off requests now include a new visibility property, indicating how the request is visible based on its associated policy. The possible visibility values are:

• Public
• Custom name
• Private

Reminder: Before accessing time off data, ensure that the service user has the necessary permissions to view this information, as you would when assigning permissions to a user in Bob.

Relevant endpoints:

• Get the details of an existing time off request.
• Get all new/deleted time off requests since the specified date.
• Read a list of who's out of the office.
• Read a list of who's out of the office today or on the specified date.

To learn more, see Time off API.

We've improved service users management to give Bob admins better control over permissions and more transparency.

Now, you can easily access detailed information about service users, including:

• Who created the user
• The date of the last session
• The date of the last token refresh
• Assigned permission groups
• Specific permissions granted

Additionally, you can add a description to each service user, quickly copy the service user ID with a single click using the clipboard icon, and export the entire table, including permissions, to a .csv or .xlsx file.

To learn more, see Manage service users.

The 'Submit a New Time Off Request' endpoint now supports requests with specific hours through the Public API. This new feature allows you to define exact times for the time off request, such as 12:15 to 14:15.

Please note that this request type allows you to provide a specific time for the entire date range.

To learn more, see Submit a new time off request.

To support users who want to update employee data via the Public API, we have published a new article that covers all you need to know when using the 'Update company employee' endpoint.

1. The steps to update employee fields via the API.
2. Fetching field metadata and data and finding the field's JSON structure.
3. How to set Service Users permissions.
4. How to update custom columns.
5. The difference between fields and columns.

Whether you're already deep into your development process or just getting started, we hope this guide becomes a valuable resource.

To learn more, see Update employee data.

The endpoints that list an employee's work entries were updated to accurately reflect the fields being returned in the response by this endpoint, and include additional error codes being returned.

To learn more, see the endpoints:

• List employee's work history.
• List work history for a list of employees.

We’ve improved the 'Read Company Positions' endpoint, which details Bob positions.

What's new

• New Fields Added: The response now includes:
  • '/position/hasOpenRequests': This field shows whether there are any pending update requests that, if approved, could change the position's data in the future. This field can also be used to filter the results.
  • '/position/id': This field shows the backend ID of this position in the database. It can also be used to filter the results.
  • '/position/modificationDate': This field shows the last modification date for this position.
• Updated Response Schema: The response schema has been updated to reflect accurately all the fields returned by this endpoint.

To learn more, see Workforce Planning > Read company positions endpoint.

We’ve enhanced our Public API documentation by adding comprehensive Working Patterns structure details, including the new Bi-Weekly working pattern, across relevant endpoints.

Here’s what’s new:

1. Expanded JSON Response Details: The documentation now includes comprehensive details on employee working patterns in the JSON responses for these endpoints:
   • List employment history for a list of employees
   • List employee's employment history.
2. New Article Published: We’ve released a new article, Working Patterns in the Public API which guides you on how to fetch and process an employee’s working patterns using the Public API.

We have made some updated to the 'Task Events Webhooks' documentation to better reflect the payload structure, and added best practices for utilizing these events effectively.

What's new

• Updated payload information: The payload sample for a task status update now includes more updated information that better reflects the actual payload being returned.
• Best practices: We've added a best practices comment, emphasizing the importance of using these events primarily as notifications. Given that some fields in the payload, such as task descriptions or titles, may contain truncated values if they exceed a certain length, it is crucial to follow these guidelines to ensure accurate data handling.

To learn more, see Employee Task Events.

We have made some updated to the 'Read the public profile section of all active employees' endpoint. This endpoint returns a predefined list of fields for all active employees that the service user can access.

What's new

• The endpoint's description now includes references to articles about permissions and how to read employee data.
• The response schema has been updated to accurately reflect the fields being returned by this endpoint.

To learn more, see Read the public profile section of all active employees.