Appwrite Cloud API
/v1/databases* version retirement
Deprecated, no dateSubscribe to Appwrite Cloud APIShare
Appwrite Cloud API has deprecated the Databases API without announcing a shutdown date. This deprecation affects all calls matching /v1/databases*, with Appwrite Cloud API noting that document-based methods will no longer receive major upgrades. After shutdown, these calls will fail.
Calls it hits
/v1/databases*
What to use instead of these calls
Move to the TablesDB API under /v1/tablesdb using databases, tables, columns, and rows instead of /v1/databases with collections, attributes, and documents. Your existing data stays where it is.
In Appwrite Cloud API's words
The old document-based methods are now deprecated and will no longer receive major upgrades.
Facts
- API
- Appwrite Cloud API
cloud.appwrite.io - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Appwrite Cloud API's own pages
Questions
When does this change take effect?
Appwrite Cloud API deprecated /v1/databases* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Appwrite Cloud 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.