OpenAPI 3.0: How to Design and Document APIs with the Latest OpenAPI Specification 3.0

Clear explanation. Thanks 🙏

Within last 2 days I was searching for a resource to learn open API specification and swagger and this is the best tutorial I had ever found. very straight forward and to the point. Thanks for this content.

Bonjour je suis nouvelle sur les api rest et il m'a été demandée de réaliser la documentation open Api d'un diagramme de classe je voudrais savoir comment on fait

Excellent

An Indian and an American I think!!

Your demo was great, why? first you showed in action. and second you explained clearly what we can do. only limited by our imagination.

Thank you so much

Is they are any way to hide Schema/Models from API Documentation in SwaggerHub?

Thank you very much for sharing this knowledge. Appreciated!

Very clear, thank you.

Next question is, how to use it OFFLINE ?

The question is, why I need OpenAPI 3.0 ? Cause every company have own requirements.

can u share best practices of openAPI Specification

can we hide parameters from the UI?

Nice ! Short,crisp and clear

Hi I liked the video. Thanks for sharing. I have a specific question: if we have a crud operation to return true/false, how we will modify the response for it?
Also how to add the pagination to the specific crud operation let's say GET operation?
Any help on that will be much appreciated..

Excellent tutorial for the beginners...

fdchgegfx

great explanation with practical point of view.

Dear All/Host of this Video,
Good you please provide details about How to secure this REST API while it is being hosted in public domain?

Here, I can not found answers, what I'm looking for. I have several queries. It will really help me if anyone can answer.
1) Suppose, I have a schema for Project model which contains 20 properties. Now for my project-dropdown API I only need 3 properties from the schema then how I can refer the schema and pick few properties only?

2) I have 2 schemas, one for Project with 20 properties and another one is Task with 10 properties. Now for ProjectDetails API I have response something like { id: 1, name: "ProjectName", tasks: [ {id: 1, name: "TaskName"} ] } Now how I can accomplish this nested object by referring both individual schema which are Project and Task

3) Can I have search box in Swagger UI to filter APIs?

"Your API's no longer a black box, there's actually a RESTful interface that allows your clients to actually interact with the data or service you want to expose." Tell me you don't understand what a black box is without saying you don't understand what a black box is.

It was really a great introduction.

This is just what I needed to learn how to create an API spec. Straight to the point. Thank you!

Can someone share how to map response with Spring framework Page.
Eg: Page<ResoponseObj>

Well structured, great explanation, and excellent example! Saves time reading myriads of documentations.

How I can secure the nodejs generated stub

Great video :)

Very clear and up to the point. Just shows how documentation is SO important

amazing content friend

Great intro, thank you.

Preview window shows: "We're sorry, but an error occured in this component. Please check the console for details."

Quite descriptive

Blessed tutor. Thanks!

Nice demo

Simply cool. It certainly gives a jump start to API Development especially with 3.0. Thanks!

Thank you for explaining this so well! Needed it.

Excellent video

Thanks for the great tutorial. How do i use OAuth2 client credentials for secure server to server communication? I cant find a proper tutorial or documentation for this. Most of them has their focus on user interaction.

Bro, why you generating swagger docs by hand?

Can anyone help to understand how to test the OpenAPI?

Good presentation... have a question... "servers" tag, is it mandatory to define the host servers in the open api yaml definition file? maybe when we do publish these apis to be used through URLs, but most of the cases (dev, test, etc) while defining the APIs these info is not static isn't it?

Awesome explanation!!! Thank you so much and shout out to the swagger team ;)

Well explained..... Thanks for sharing wonderful knowledge