umbraco-openapi-client

To prevent 401 Unauthorized errors when calling Umbraco backoffice APIs, generate a TypeScript OpenAPI client configured with Umbraco's UMB_AUTH_CONTEXT token-based authentication. This ensures your backoffice frontend code carries the proper bearer token for custom C# controller requests.

To generate a TypeScript client from swagger.json for Umbraco, use a Node generation script that fetches the Swagger specification and outputs type-safe service methods. You then configure this generated client with baseUrl, credentials, and the token from getOpenApiConfiguration().

You need an OpenAPI client for custom Umbraco backoffice UI features to achieve type-safe API calls when loading and mutating data. It replaces brittle raw fetch calls with generated TypeScript types and service methods for your custom C# [BackOfficeRoute] endpoints.

Using raw fetch calls instead of a generated OpenAPI client in Umbraco leads to brittle integrations and potential authentication failures. Generating an auth-safe OpenAPI TS client ensures proper bearer token configuration via UMB_AUTH_CONTEXT and provides type-safe access to your endpoints.

Yes, the generated Umbraco OpenAPI client supports token-based authentication by consuming the UMB_AUTH_CONTEXT. You configure the client entry point with baseUrl, credentials, and the authentication token obtained through Umbraco's getOpenApiConfiguration() settings.