Cloudbeds API
/api/v1.1/* version retirement
Deprecated, no dateSubscribe to Cloudbeds APIShare
Cloudbeds API deprecated version 1.1 without a shutdown date. This deprecation impacts all calls to /api/v1.1/*. After retirement takes effect, requests to these endpoints will fail.
Calls it hits
/api/v1.1/*
What to use instead of these calls
Call the same methods under Cloudbeds API v1.2 instead. The move requires more than changing an identifier, as identifiers such as propertyID, guestID, and itemID become strings.
In Cloudbeds API's words
We're contacting you to inform you that Cloudbeds API version 1.1 will be deprecated on March 31st, 2025. For that reason, you must transition to Cloudbeds API v1.2 by that date.
Facts
- API
- Cloudbeds API
api.cloudbeds.com - Kind
- Version retirement
- Announced
- January 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 /api/v1.1/* 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
GET /api/v1.2/getAdjustmentEndpoint removal 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.