umbraco-openapi-client
Umbraco OpenAPI Client Setup
CRITICAL: Why This Matters
NEVER use raw fetch() calls for Umbraco backoffice API communication. Raw fetch calls will result in 401 Unauthorized errors because they don't include the bearer token authentication that Umbraco requires.
ALWAYS use a generated OpenAPI client configured with Umbraco's auth context. This ensures:
- Proper bearer token authentication
- Type-safe API calls
- Automatic token refresh handling
When to Use This
Use this pattern whenever you:
- Create custom C# API controllers with
[BackOfficeRoute] - Need to call your custom APIs from the backoffice frontend
- Build trees, workspaces, or any UI that loads data from custom endpoints
Setup Overview
More from umbraco/umbraco-cms-backoffice-skills
umbraco-backoffice
Umbraco backoffice extension customisation - complete working examples showing how extension types combine
185umbraco-controllers
Understand and create controllers in Umbraco backoffice (foundational concept)
171umbraco-extension-template
Create new Umbraco backoffice extensions using the official dotnet template
170umbraco-dashboard
Implement dashboards in Umbraco backoffice using official docs
170umbraco-quickstart
Quick setup for Umbraco extension development - creates instance, extension, and registers it
168umbraco-property-editor-ui
Implement property editor UIs in Umbraco backoffice using official docs
165