This feature is currently in beta and may change as we continue to improve it.
You can now connect agents like Claude desktop, Cursor, Microsoft Copilot Studio, and Visual Studio Code to Bob using the HiBob MCP server, giving them access to:
Read and update employee data
Access time off records
Retrieve and manage tasks
If you’re already working with MCP, you know the drill - just add the HiBob server and go.
As our time off request capabilities evolve, we've enhanced the GET Time off request by ID endpoint with improved field descriptions to better reflect the values that may be returned when retrieving a time off request.
These are documentation-only changes, with no impact on the actual API behavior. The goal is to better reflect the structure and values already returned in the response payload.
What's included
Updated category title: The API category name has changed from Time & Attendance API to Time Off & Attendance API for clarity.
Additional request types: The requestType field now reflects the wider range of values supporting more flexible time off options:
days: The request spans X full days.
hours: The request is for X hours during the day (applies only to policies measured in hours).
portionOnRange: The request is for every morning or afternoon during the selected date range.
hoursOnRange: The request is for X hours each day in the date range.
differentDayDurations: The request is for a different number of hours on each day in the range.
specificHoursDayDurations: The request is for specific hours per day.
percentageOnRange: The request is for X% of each day in the date range.
New durations field: Added a durations array to reflect granular time off requests that vary across the selected days.
We’ve removed the get-employee header from employee webhooks payload.
This header included a direct link to the now-deprecatedGET Employee API and is no longer relevant for current integrations.
It was originally added to help customers retrieve full employee data, but going forward, the employee search endpoints should be used instead.
Why this change?
This update ensures webhook payloads reflect supported and scalable API usage. All related references have been removed from our documentation to avoid confusion..
Who is affected?
Any systems relying on this header should be updated to use the search endpoints to retrieve employee data.
Previously, service users could access employee profile pictures without being assigned to any permission group.
What this change?
Moving forward, visibility of avatars through the API is restricted based on the About category permission, aligning it with other employee data access rules.
To allow the service user to read the avatar, you now need to enable the permission:
People's data > About > View selected employees' About sections.
Workforce Planning now supports prorated position costs. When you define your fiscal year and add an end date to a position, the platform automatically calculates the cost based on how long the position is active during that financial cycle.
You can now access these details through the Public API:
The /position/endEffectiveDate field is available on the position object. It indicates when the position’s cost should stop being included in planning.
The /position/positionBudget/proRatedCostCurrencyValue field is available on the position budget. It shows the calculated prorated cost of the position, converted to your company’s base currency.
This gives you API visibility into how position costs are prorated, helping you align external reports or tools with your workforce planning data.
We’re experimenting with short audio recaps and deep dives to make our documentation more accessible. The first ones are live at the end of the article:
Each provides a quick, AI-generated summary that highlights the main points.
We're curious if this format is useful to you, so feel free to share feedback via the vote option at the bottom of the article (and please include your email so we can follow up!).
Final Notice: API Get Endpoints Shutdown by May 6, 2025
The Get endpoints listed below will be completely shut off by May 6, 2025.
GET api.hibob.com/v1/people
GET api.hibob.com/v1/people/XXXX
If your organization is still using the deprecated endpoints, action is required to prevent disruptions. Any processes relying on these endpoints will stop working, potentially impacting your operations. Follow the instructions below to migrate to the new Search API to replace the two GET endpoints.
❗️
Final Notice: API Access Tokens Shutdown by May 6, 2025
The "API Access Token" authentication method will be completly shut off by May 6, 2025.
Companies using this legacy method should transition to the Service User method immediately. From this date, API integrations using API Access Tokens will stop working. Any system or process that relies on API Access Tokens will fail, potentially causing disruptions.
