The API documentation indicates that the the Vault Management API is “accessible from the Bitwarden CLI” and doesn’t mention other methods for accessing the API. Thus, unless you have found information to the contrary, I would tend to believe that using the CLI is required.
The article from the Help Center clarifies the differences between the Public API and the Vault Management API, and states explicitly that to use the latter, you must first “use the serve command from the CLI to start a local express web server from which to make requests”:
Could i make a feature or documentattion request ? Technically, if the CLI uses the API, I don’t see what would prevent from calling the API in another language : curl, Python, or any language able to make an http request.
bw serve is required to spin up a local web server that will handle end-to-end encryption. You can then use curl, Python, etc. to make HTTP requests against that server (default endpoint: http://localhost:8087). A little more detail is provided in this comment:
I see. thanks for the additional details. I hadn’t realized using bw serve was a necessary step. I would agree with the comments left on the other post. It makes it much heavier to integrate. Initially, I wanted to build a simple Python library to integrate with bitwarden password manager but this requires to pre-install the CLI first, launch the server locally and call the API endpoints locally. I had wished the CLI commands would be available as REST endpoints from bitwarden.com or bitwarden.eu.