umbraco-openapi-client

Fix 401 Unauthorized errors in Umbraco extensions by configuring the OpenAPI TypeScript client with the UMB_AUTH_CONTEXT to automatically include bearer token credentials in fetch calls. This ensures authenticated communication with custom BackOfficeRoute controllers.

Generate a TypeScript client for an Umbraco backoffice API by exposing Swagger for your custom routes and using @hey-api/openapi-ts to generate type-safe methods from the swagger.json file. This enables reliable data integration.

Yes, Umbraco backoffice API communication requires bearer token auth to avoid unauthorized failures. Extension development must consume the UMB_AUTH_CONTEXT to set base URLs and credentials for authenticated fetch calls to custom controllers.

The best way to configure authenticated API calls is setting the generated OpenAPI client's base URL and credentials using Umbraco's auth context in the extension entry point. This avoids unmaintainable, unsafe unauthenticated fetch calls.

Unauthenticated fetch calls fail because they lack the required bearer token. Configure the OpenAPI client in your extension entry point using host.consumeContext(UMB_AUTH_CONTEXT, ...) to set baseUrl and credentials for authorized data access.