Cloudbeds API
GET /api/v1.2/getAdjustment endpoint removal
Deprecated, no dateSubscribe to Cloudbeds APIShare
Cloudbeds API deprecated the GET /api/v1.2/getAdjustment endpoint without specifying a shutdown date. Subsequent calls to this endpoint fail. This change impacts all integrations currently issuing requests to this specific route under version 1.2.
Calls it hits
GET /api/v1.2/getAdjustment
What to use instead of these calls
Read transactional data through the Accounting API instead by calling POST api.cloudbeds.com/accounting/v1.0/transactions with filters including source_kind, source_identifier, and date ranges.
In Cloudbeds API's words
Today we are announcing that these changes will take effect on December 1st, 2025, and the following API endpoints will be deprecated from v1.2
Facts
- API
- Cloudbeds API
api.cloudbeds.com - Kind
- Endpoint removal
- Announced
- June 1, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Cloudbeds API's own pages
Questions
When does this change take effect?
Cloudbeds API deprecated GET /api/v1.2/getAdjustment without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Cloudbeds 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 Cloudbeds API 5
-
No date
/api/v1.1/*Version retirement Deprecated, no date -
No date
GET /api/v1.2/getAdjustmentsEndpoint removal Deprecated, no date -
No date
GET /api/v1.2/getHouseAccountDetailsEndpoint removal Deprecated, no date -
No date
GET /api/v1.2/getPaymentsEndpoint removal Deprecated, no date -
No date
GET /api/v1.2/getTransactionsEndpoint 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.