umbraco-openapi-client

Sets up authenticated OpenAPI clients for Umbraco backoffice frontend integrations.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-openapi-client-kraftvaerk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-openapi-client
Source: https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy/tree/main/Kraftvaerk.Umbraco.Alchemy.Frontend/.agents/skills/umbraco-openapi-client
Command: npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-openapi-client-kraftvaerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures secure and authenticated API calls within the Umbraco backoffice, preventing common 401 Unauthorized errors and simplifying frontend development.

Core Features & Use Cases

  • Secure API Communication: Automatically handles bearer token authentication for custom Umbraco APIs.
  • Type-Safe Development: Leverages generated OpenAPI clients for robust and maintainable code.
  • Use Case: When building a custom section in Umbraco that needs to fetch data from your own C# API controller, this Skill provides the essential setup to ensure your frontend code can communicate reliably with the backend.

Quick Start

Configure the OpenAPI client with Umbraco's auth context in your entry point file.

Frequently Asked Questions about umbraco-openapi-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make authenticated API calls from the Umbraco backoffice frontend?

Authenticated API calls in the Umbraco backoffice require a configured OpenAPI client that handles bearer token authentication and automatic token refresh, replacing raw fetch requests with type-safe operations.

Why does my custom Umbraco API controller return 401 Unauthorized errors?

Unauthorized 401 errors in custom Umbraco APIs typically occur when frontend requests lack proper bearer token authentication, which an OpenAPI client setup resolves by integrating Umbraco's auth context automatically.

How do I generate a TypeScript OpenAPI client for a custom C# API in Umbraco?

Generating a TypeScript OpenAPI client for a custom C# API involves using Swagger or OpenAPI specifications to create type-safe frontend code, ensuring reliable communication with your Umbraco backend controllers.

Does the Umbraco OpenAPI client handle automatic token refresh for frontend integrations?

Yes, the Umbraco OpenAPI client handles automatic token refresh for frontend integrations, ensuring continuous authenticated access to custom backend APIs without manual token management or session interruptions.

What is the best way to secure custom API communication in an Umbraco backoffice section?

Securing custom API communication in an Umbraco backoffice section is best achieved by using a generated OpenAPI client with type-safe requests and built-in bearer token authentication instead of raw fetch calls.