1 minute read

These days I am more into creating backend projects which include microservices.But if anyone wants to test these services one needs postman or do the old classic way of curl command.

Both do the job brilliantly but what if I wanted some user who doesn’t want to install postman or use curl and still wants to test my live APIs thru the browser? I came across this swagger open API specification and this is a really handy tool!

In layman’s terms, Swagger OpenAPI specification provides API documentation for REST APIs. An OpenAPI file allows you to describe all the APIs within the project and even lets you try out the APIs!

Available endpoints can be /projectApi and all operations on each endpoint which can GET /getProjectApi , POST /insertProjectApi , DELETE /deleteProjectApi .


Also, integration of swagger open API is pretty painless in spring boot and it lets users try out the APIs within the browser without any installation of any software from the user (sounds pretty convenient and sweet to me)

In this post, I will describe how I integrated swagger open API in Spring boot project.First you need a spring boot project having basic dependcies using Spring Initializr https://start.spring.io/ or you could use this project used in the example here

First add the springdoc-openapi-ui dependency to pom.xml:

Then run the application and check the below url to check open api specification


You should be able to see something like this


You can also add a custom path by adding entry in application.properties file

and now check the url http://localhost:8080/api


For the web ui,have the same maven dependency in pom.xml and lets customize the ui path by adding the following entries in application.properties file.


Check http://localhost:8080/swagger for web UI.To show you in this example we have a following apis in the controller.

So the swagger ui look something like this


Also json docs will be available at http://localhost:8080/api springdoc.swagger-ui.operationsSorter=method sorts the API paths in order of their HTTP methods.

You can try and test the apis from web ui too. post-eg-swagger get-eg-swagger

It also shows schema information!


Overall this is a much convenient way of setting up documentation for your apis which can be handy in some situations.

That’s all folks!