Delivery API v2: Duplicate operationId "QueryV20" in /content and /media endpoints

[DMOShareIT]

Which Umbraco version are you using?

16.2.0 and 16.3.3

Bug summary

When the Content Delivery API v2 is enabled, both the /umbraco/delivery/api/v2/content and /umbraco/delivery/api/v2/media GET endpoints generate the same operationId: "QueryV20" in the OpenAPI/Swagger JSON.
This causes conflicts in OpenAPI clients (e.g. NSwag, Swagger Codegen, OpenAPI Generator) and breaks client generation.

Specifics

Each endpoint should have a unique operationId, e.g.:

"/umbraco/delivery/api/v2/content": { "get": { "operationId": "GetContent2.0" } }
"/umbraco/delivery/api/v2/media":    { "get": { "operationId": "GetMedia2.0" } }

And what I got is:

"/umbraco/delivery/api/v2/content": { "get": { "operationId": "QueryV20" } }
"/umbraco/delivery/api/v2/media":    { "get": { "operationId": "QueryV20" } }

Steps to reproduce

Create a new Umbraco project:

dotnet new umbraco -n UmbracoBugDemo
cd UmbracoBugDemo

Update to the latest version (16.3.3): Edit your .csproj file:

<PackageReference Include="Umbraco.Cms" Version="16.3.3" />

Restore packages and build:

dotnet restore
dotnet build

Enable Delivery API v2 in appsettings.json:

{
  "Umbraco": {
    "CMS": {
      "DeliveryApi": {
        "Enabled": true,
        "ApiVersion": "v2"
      }
    }
  }
}

Run the application:

dotnet run

Access Swagger UI:

https://localhost:5001/swagger/index.html

(Port may vary; check console output)

Locate the endpoints in Swagger UI:

• GET /umbraco/delivery/api/v2/content
• GET /umbraco/delivery/api/v2/media

Download/Inspect the OpenAPI JSON:

https://localhost:5001/swagger/v1/swagger.json

Verify the issue in the JSON:

{
  "paths": {
    "/umbraco/delivery/api/v2/content": {
      "get": {
        "operationId": "QueryV20"  // ← DUPLICATE
      }
    },
    "/umbraco/delivery/api/v2/media": {
      "get": {
        "operationId": "QueryV20"  // ← DUPLICATE
      }
    }
  }
}

Expected vs. Actual

Expected:

• GetContent2.0 for /content
• GetMedia2.0 for /media

Actual:

• QueryV20 for both → Duplicate Conflict

Expected result / actual result

No response

[github-actions]

Hi there @DMOShareIT!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[kjac]

Hi @DMOShareIT 👋

Thanks for reaching out. Unfortunately, I can't reproduce this issue. I see the "query" endpoint for content with the operation ID GetContent2.0 - for media it's GetMedia2.0.

Here's a link to the full Delivery API schema from my V16.3.3: delivery-api-v16.json

I've got a feeling your setup is somehow customized. On a default install, the paths /swagger/index.html and /swagger/v1/swagger.json do not exist - the Swagger UI is at /umbraco/swagger/index.html, and the Delivery API schema is at /umbraco/swagger/delivery/swagger.json.

Could you please remove any customizations and retry this? Alternatively, provide additional steps to reproduce.

[DMOShareIT]

Hi there, thank you for looking, after 2 days we found out that it comes from

<PackageReference Include="Umbraco.UIBuilder" Version="16.1.0" />

Using this package creates this problem.

We've removed too
<PackageReference Include="Umbraco.Community.ContentAudit" Version="2.0.0-beta" />
and
<PackageReference Include="Kjac.HeadlessPreview" Version="2.0.0" />

Not needed for this project, but I dont think those are problematic but only UIBuilder. (That it will not be needed for us, but it may help find the culprit, since it doesnt seems the intended behavior I beleive)

Regarding the paths, you're correct, it was a mistake on my 1st message.

[kjac]

Hi @DMOShareIT

Thanks for digging into this 👏 I'll have someone investigate if this is a UI builder issue, and transfer the issue accordingly.

[mattbrailsford]

I can't replicate this at all.

I've tried in both our local UI Builder install working from source, and I've also tried setting up a fresh Umbraco CMS 16.2.0 install and using the UI Builder 16.1.0 nuget dependency and both times I successfully see the GetContent2.0 and GetMedia2.0 operationIds, not the QueryV20 opperationId.

[kjac]

I can confirm @mattbrailsford's findings (or lack thereof). Installing UI Builder does not affect the Delivery API schema on my local 16.3.3 site.

I'm going to close this one as we're unable to replicate. Please feel free to reopen if you find additional steps to reproduce.

[DMOShareIT]

I've tried in both our local UI Builder install working from source, and I've also tried setting up a fresh Umbraco CMS 16.2.0 install and using the UI Builder 16.1.0 nuget dependency and both times I successfully see the GetContent2.0 and GetMedia2.0 operationIds, not the QueryV20 opperationId.

Thks for looking to it, can you just try with the other 2 I mention? I did remove the 3 when I saw it was working again, I just assumed it was from UiBuilder, but it could be any of the 3.

[mattbrailsford]

Testing adding the other packages does replicate the issue. For me it looks like it's an issue with Umbraco.Community.ContentAudit. If add that in, I get the issue, if I remove it, it returns to what I'd expect