BambooHR API
POST /api/v1/reports/custom endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
BambooHR deprecated POST /api/v1/reports/custom without a shutdown date. Calls made to this endpoint will eventually fail. BambooHR API marked this legacy report endpoint as deprecated in its OpenAPI documentation and directs consumers to modern alternatives.
Calls it hits
POST /api/v1/reports/custom
What to use instead of these calls
Use Get Data from Dataset v2 via POST /api/v2/datasets/{datasetName}/data instead. You can use GET /api/v1/custom-reports/legacy-field-map to map the old field identifiers.
In BambooHR API's words
We marked two legacy report endpoints as deprecated in our OpenAPI documentation and added guidance directing consumers to their newer alternatives: - POST /api/v1/reports/custom → Get Data from Dataset v2 at POST /api/v2/datasets/{datasetName}/data - GET /api/v1/reports/{id} → Get Report by ID at GET /api/v1/custom-reports/{reportId}
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- March 18, 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/reports/custom 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.