# GET /api/v1/datasets is deprecated

BambooHR API deprecated GET /api/v1/datasets without giving a shutdown date yet.

BambooHR API deprecated GET /api/v1/datasets without a shutdown date, marking it as deprecated in its OpenAPI documentation. Calls targeting this endpoint will eventually fail once it is removed. This change directly affects any integrations relying on the v1 Dataset discovery endpoints.

## What to use instead

Use GET /api/v1_2/datasets instead.

- API: BambooHR API (*.bamboohr.com)
- Kind: Endpoint removal
- Announced: March 25, 2026
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `GET /api/v1/datasets`
- 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-datasets-is-deprecated/

## BambooHR API's words

> We marked the following Dataset discovery endpoints as deprecated in our OpenAPI documentation and added guidance directing consumers to the v1.2 versions: - GET /api/v1/datasets → GET /api/v1_2/datasets - GET /api/v1/datasets/{datasetName}/fields → GET /api/v1_2/datasets/{datasetName}/fields - POST /api/v1/datasets/{datasetName}/field-options → POST /api/v1_2/datasets/{datasetName}/field-options

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