Feature Request
SimpleLogin and Addy.io services both allow providing custom endpoints for self-hosted instances, however there are numerous other projects that would like to integrate with Bitwarden, such as mailcow.
Expecting Bitwarden to add support for all these different APIs and maintain them as changes are made seems excessive, so what if Bitwarden instead lays out a simple API specification, and allow any app that desires to implement it however they please? Then the Bitwarden apps can have a “generic” service, similar to the existing Addy.io and SimpleLogin ones, but using a stable API that Bitwarden controls instead of some 3rd party.
Design
I was imagining having a dedicated path, with whatever endpoints Bitwarden needs under that path. For example, https://example.com/whatever/bitwarden/api/v1/<endpoint>. This allows it to easily be adjusted to fit whatever backend API already exists, as they may conflict if the path cannot be customized. The user can provide the direct path to the API in the Bitwarden clients, or the Bitwarden client can auto-discover the path via a .well-known declaration, allowing the users to only specify the domain.
For now, a simple “add random alias” endpoint is all that’s needed, but maybe Bitwarden could implement basic alias listing/deletion or something too if it’s a standardized API.