Multiple swagger related endpoints published

[Enifs]

GET /swagger (io.federecio.dropwizard.swagger.SwaggerResource)
GET /swagger.{type:json|yaml} (io.swagger.jaxrs.listing.ApiListingResource)

I don't know if this is expected behavior or a bug, but in my use case I don't need the second endpoint at all. Is there a way how to get rid of it?

Thanks in advance!

[ravidesai47]

Hi @Enifs,

This is expected behavior. The two endpoints serve distinct and necessary purposes:

GET /swagger: Serves the Swagger UI (the HTML/JS interface).

GET /swagger.{type:json|yaml}: Generates the actual API metadata (the OpenAPI specification) that the UI consumes.

The Swagger UI requires the underlying JSON/YAML data to function. When you load the UI in the browser, it makes a background request to the second endpoint to retrieve the list of endpoints and their details. If you remove the ApiListingResource, the UI will have no data to display.