BambooHR API
POST /api/v1/login endpoint removal
Deprecated, no dateSubscribe to BambooHR APIShare
On May 12, 2025, BambooHR API marked POST /api/v1/login as deprecated in its OpenAPI documentation without announcing a shutdown date. Calls hitting this endpoint will eventually fail. BambooHR API announced this change alongside guidance recommending OAuth 2.0 for new integrations.
Calls it hits
POST /api/v1/login
What to use instead of these calls
Authenticate with OAuth 2.0 using an app registered on developers.bamboohr.com, alongside authorize.php and token.php on the company's domain, instead of generating API keys through /api/v1/login.
In BambooHR API's words
We marked POST /api/v1/login as deprecated in our OpenAPI documentation and added guidance recommending OAuth 2.0 for new integrations.
Facts
- API
- BambooHR API
*.bamboohr.com - Kind
- Endpoint removal
- Announced
- May 12, 2025
- 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/login 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/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.