BambooHR API
PUT /api/v1/time_off/requests/{id}/status endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
BambooHR has deprecated the PUT /api/v1/time_off/requests/{id}/status endpoint without announcing a shutdown date. BambooHR API updated its documentation to direct callers toward newer process resources. Calls to this endpoint will eventually fail once it is removed.
Calls it hits
PUT /api/v1/time_off/requests/{id}/status
What to use instead of these calls
Use POST /api/v1/time-off/requests/{id}/approvals, /denials or /cancellations instead of setting the status.
In BambooHR API's words
We marked the following endpoint as deprecated in our OpenAPI documentation and added guidance directing consumers to the newer process resources: PUT /api/v1/time_off/requests/{requestId}/status
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- August 17, 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/time_off/requests/{id}/status 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.