BambooHR API · Endpoint removal
GET /api/v1/reports/{} is deprecated
Deprecated, no date
BambooHR API deprecated GET /api/v1/reports/{} without giving a shutdown date yet.
What to use instead of these calls
Use Get Report by ID, GET /api/v1/custom-reports/{reportId}; GET /api/v1/custom-reports/legacy-id-map and legacy-field-map map the old ids and fields.
Calls it hits
GET /api/v1/reports/{}
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
More from BambooHR API
- GET /api/v1/datasets is deprecated Deprecated, no date
- GET /api/v1/datasets/{}/fields is deprecated Deprecated, no date
- GET /api/v1/employees/{}/time_off/policies is deprecated Deprecated, no date
- GET /api/v1/performance/employees/{}/goals/aggregate is deprecated Deprecated, no date
- POST /api/v1/datasets/{} is deprecated Deprecated, no date
- POST /api/v1/datasets/{}/field-options is deprecated Deprecated, no date