By default the plugin doesn't provide any content-api routes except for the ones used to authenticate. However, it is possible to extend the plugin and retroactively expose some content-api routes through the extensions folder. This might come in handy if you want to include your Better Auth users / organization in the Strapi content-api. That way you can use that content to render profile pages on your website e.g.
We don't want to provide these endpoints by default, but we should document how one can extend the plugin to get this functionality. In the documentation we should also put a warning banner saying that you should be careful with leaking sensitive data through your public Strapi API. You will likely have to sanitize the the response at some point.
By default the plugin doesn't provide any content-api routes except for the ones used to authenticate. However, it is possible to extend the plugin and retroactively expose some content-api routes through the
extensionsfolder. This might come in handy if you want to include your Better Auth users / organization in the Strapi content-api. That way you can use that content to render profile pages on your website e.g.We don't want to provide these endpoints by default, but we should document how one can extend the plugin to get this functionality. In the documentation we should also put a warning banner saying that you should be careful with leaking sensitive data through your public Strapi API. You will likely have to sanitize the the response at some point.