# GET /api/v1/reports/{} is deprecated

BambooHR API deprecated GET /api/v1/reports/{id} without giving a shutdown date yet.

BambooHR API deprecated GET /api/v1/reports/{id} without a shutdown date. The deprecation was announced on March 18, 2026. Once removed, affected requests fail.

## What to use instead

Use Get Report by ID at GET /api/v1/custom-reports/{reportId}. Endpoints GET /api/v1/custom-reports/legacy-id-map and legacy-field-map map the old ids and fields.

- API: BambooHR API (*.bamboohr.com)
- Kind: Endpoint removal
- Announced: March 18, 2026
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `GET /api/v1/reports/{id}`
- Source: [Announcement](https://documentation.bamboohr.com/docs/past-changes-to-the-api)
- Verified: November 6, 2026, against BambooHR API's own pages
- Page: https://www.okapi.bot/providers/bamboohr-api/breaking-changes/get-api-v1-reports-is-deprecated/

## 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}

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent