umbraco-repository-pattern

To implement the repository pattern in the Umbraco backoffice, use Umb controller and context base classes to abstract data access. Register the repository in the umbExtensionsRegistry to enable consistent CRUD operations and separate what the backoffice does from how it fetches data.

You get 401 Unauthorized errors during Umbraco backoffice data access when using raw fetch instead of the generated OpenAPI client. You must use the OpenAPI client integrated with the Umbraco auth context to ensure safe API authentication for your repository.

The best way to structure Umbraco backoffice extensions for list and tree data is building repository, view-model, and context flows. This separates data retrieval from state caching, supporting list, single-item, create/update/delete, and tree repository scenarios reliably.

Yes, you need TypeScript to build Umbraco backoffice repositories effectively. TypeScript enables you to define strongly typed data sources, stores, and repository contracts that wire cleanly into Umb controller base classes and the umbExtensionsRegistry.

An Umbraco repository interacts with a data source and store by acting as a stable entry point for the UI. The repository delegates data fetching to the data source via the OpenAPI client and manages cached state through the store, ensuring clean separation of concerns.