What is the new way of calling the umbraco api (contentResource) to fetch data, is there none? Do devs need to create their own controllers to fetch data from Umbraco? I'm in need of fetching node content from Umbraco to verify it is valid, and I'm not seeing any kind of backoffice api for fetching content.

Content will now come from the Content Delivery API (https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api) and most backoffice API calls will go through the Management API (https://docs.umbraco.com/umbraco-cms/reference/management-api). Both have Swagger endpoints so you can test them out before calling them in code

thanks, just found this myself, the replacement is the management api.

Have you tried the Swagger endpoint ?

Yes. Swagger is great for showing api details, but doesn’t show how to actually consume secured apis. I think I might understand now. In the past, you could just inherit from umbracoAuthorizedApiController. Now umbraco expects you as a developer to gather and send an oauth request.

> Yes. Swagger is great for showing api details, but doesn’t show how to actually consume secured apis.

@Aaron Sawyer yes, if you are wanting to use the Management API or your own API in a new backoffice package, your best bet would be to generate a client with

openapi-ts

and then authenticate like this: https://dev.to/kevinjump/umbraco-early-adopter-gotcha-authing-requests-4m63

Depending on what you need to do with the content, you can always use the CMS' generated services, rather than creating your own API endpoint. Import it into your component, wrap the call in

tryExecuteAndNotify

, and Bob's your mother's brother.

lol. What do you mean by the CMS generated services, I'm guessing you mean the existing management api? Also, I'm not intending on making a package, just adding custom backoffice functionality for a single site (I assume this really doesn't make a difference, the same steps need to be taken).

Well depends what you are doing. Do you just need to fetch a piece of content or do you need some really custom JSON response for your needs?

I need custom json. This is a very common occurrence for us, we build some backoffice button for example, it calls a c# controller, and returns json. Naturally we want to lock down that c# controller to only backoffice users. This isn't a package, it is only for a single website installation. I'm not 100% sure I'm doing this the right way. I am following the early adopter's guide by kevin jump, and I'm currently attempting to run the openapi-ts command, so I can get the interface, to call my controller with the proper umbraco oauth authentication. Seems like a lot for just calling a single controller endpoint to do some custom thing on click.

Well you dont need to have a strongly typed TypeScript client for your custom API MGMT controller.

Thanks Warren. I don't fully understand the need for repositories, contexts, and services and how thery relate, but I'll look into it. In the meantime I was able to get what I needed working rather easily. import { UMB_AUTH_CONTEXT } from '@umbraco-cms/backoffice/auth'; ... this.consumeContext(UMB_AUTH_CONTEXT, async (auth) => { if (!auth) return; const umbOpenApi = auth.getOpenApiConfiguration(); await umbOpenApi.token().then(function (authToken) { //execute oauth 2 secured endpoint fetch('/my-api/v1/get-stuff/?guidkey=' + guidKey + '&culturecode=' + cultureCode, { method: 'GET', headers: { 'Authorization': 'Bearer ' + authToken, 'Accept': 'application/json' } }).then(function (resp) { resp.json().then(function (result) { //have json data console.log(data); }); }); }); });

Yep the repo and store is overkill in most cases IMO

what I was missing was understanding where to get the token from. it's easy to get the token from UMB_AUTH_CONTEXT

Yep

I see, and that is the benefit of using the openapi-ts generated data?

Yep with your api defined as OpenAPI spec

ok, thanks. This has been very helpful

So means you catch early on whilst in your code editor