If you’re developing microservices, you’re definitely using some form of API Gateway. And if you’re developing in a .NET Core ecosystem, it’s maybe to be Ocelot.

Ocelot is a great project to create your own API Gateway. Unfortunately, it does not allow one important thing, to integrate the swagger documentations of your microservices into one place. (see documentation).

MMLib.SwaggerForOcelot

The MMLib.SwaggerForOcelot package provides a way to achieve this. It allows you to view microservices documentation directly via Ocelot API Gateway. Document your entire system in one place. MMLib.SwaggerForOcelot transforms microservice documentation to be correct from the Gateway API point of view. So it modifies the addresses and removes endpoints that are not routed out via the API Gateway.

How to start?

Configure SwaggerGen in your downstream services. Follow the SwashbuckleAspNetCore documentation. Install Nuget package into yout ASP.NET Core Ocelot project. dotnet add package MMLib.SwaggerForOcelot Configure SwaggerForOcelot in ocelot.json . { "Routes" : [ { "DownstreamPathTemplate" : "/api/{everything}" , "UpstreamPathTemplate" : "/api/contacts/{everything}" , "ServiceName" : "contacts" , "SwaggerKey" : "contacts" }, { "DownstreamPathTemplate" : "/api/{everything}" , "UpstreamPathTemplate" : "/api/orders/{everything}" , "ServiceName" : "orders" , "SwaggerKey" : "orders" } ], "SwaggerEndPoints" : [ { "Key" : "contacts" , "Config" : [ { "Name" : "Contacts API" , "Version" : "v1" , "Url" : "http://localhost:5100/swagger/v1/swagger.json" } ] }, { "Key" : "orders" , "Config" : [ { "Name" : "Orders API" , "Version" : "v1" , "Url" : "http://localhost:5200/swagger/v1/swagger.json" } ] } ], "GlobalConfiguration" : { "BaseUrl" : "http://localhost" } } In the ConfigureServices method of Startup.cs register the SwaggerForOcelot generator. services . AddSwaggerForOcelot ( Configuration ); In Configure method insert the SwaggerForOcelot middleware to expose interactive documentation. app . UseSwaggerForOcelotUI ( Configuration )

The SwaggerEndPoints section contains the configurations needed to obtain documentation for each microservice. The Key property is used to pair with the ReRoute configuration. Name is displayed in the combobox. Url is the address for the microservice documentation. If you have multiple versions of your api, you can take this into account in the Config section. For example:

"Key" : "orders" , "Config" : [ { "Name" : "Orders API" , "Version" : "v1" , "Url" : "http://localhost:5200/swagger/v1/swagger.json" }, { "Name" : "Orders API" , "Version" : "v2" , "Url" : "http://localhost:5200/swagger/v2/swagger.json" } ]

Show your microservices interactive documentation http://ocelotserviceurl/swagger .

Learn more in the repository MMLib.SwaggerForOcelot.