BambooHR API
PUT /api/v1/employees/{id}/time_off/policies endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
On July 8, 2026, BambooHR API deprecated the endpoint PUT /api/v1/employees/{id}/time_off/policies without a shutdown date. Calls made to this route will eventually fail. BambooHR API marked this route as deprecated in OpenAPI documentation and directs developers away from the v1 path.
Calls it hits
PUT /api/v1/employees/{id}/time_off/policies
What to use instead of these calls
Use PUT /api/v1_1/employees/{employeeId}/time_off/policies instead.
In BambooHR API's words
We marked the following v1 endpoints as deprecated in our OpenAPI documentation and added guidance directing new development to their v1.1 equivalents: - POST /api/v1/employees/{id}/tables/{table} - POST /api/v1/employees/{id}/tables/{table}/{rowId} - GET /api/v1/employees/{employeeId}/time_off/policies - PUT /api/v1/employees/{employeeId}/time_off/policies
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- July 8, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against BambooHR API's own pages
Questions
When does this change take effect?
BambooHR API deprecated PUT /api/v1/employees/{id}/time_off/policies without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: BambooHR API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from BambooHR API 10
-
No date
GET /api/v1/datasetsEndpoint removal Deprecated, no date -
No date
GET /api/v1/datasets/{id}/fieldsEndpoint removal Deprecated, no date -
No date
GET /api/v1/employees/{id}/time_off/policiesEndpoint removal Deprecated, no date -
No date
GET /api/v1/performance/employees/{id}/goals/aggregateEndpoint removal Deprecated, no date -
No date
GET /api/v1/reports/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v1/datasets/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v1/datasets/{id}/field-optionsEndpoint removal Deprecated, no date -
No date
POST /api/v1/employees/{id}/tables/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v1/employees/{id}/tables/{id}/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v1/loginEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.