BambooHR API
POST /api/v1/datasets/{id}/field-options endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
BambooHR deprecated POST /api/v1/datasets/{id}/field-options on March 25, 2026, without a shutdown date. Calls to this endpoint will eventually fail once the removal takes effect. BambooHR API has marked the endpoint as deprecated in its OpenAPI documentation.
Calls it hits
POST /api/v1/datasets/{id}/field-options
What to use instead of these calls
Use POST /api/v1_2/datasets/{datasetName}/field-options instead.
In 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
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- March 25, 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/datasets/{id}/field-options 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/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 -
No date
POST /api/v1/reports/customEndpoint 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.