BambooHR API
POST /api/v1/time_tracking/projects endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
The legacy endpoint POST /api/v1/time_tracking/projects has been deprecated without a shutdown date. The change was announced on July 30, 2026. Once removed, requests to this endpoint will fail.
Calls it hits
POST /api/v1/time_tracking/projects
What to use instead of these calls
Use POST /api/v1/time-tracking/projects, using a hyphen instead of an underscore, which is the current Create Time Tracking Project endpoint.
In BambooHR API's words
We marked the legacy Create Time Tracking Project endpoint as deprecated in our OpenAPI documentation: POST /api/v1/time_tracking/projects
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- July 30, 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 POST /api/v1/time_tracking/projects 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.