OpenAPI 3.0: How to Design and Document APIs with the Latest OpenAPI Specification 3.0
HTML-код
- Опубликовано: 26 сен 2017
- The OpenAPI Specification (OAS), based on the original Swagger 2.0 specification, has emerged as the world’s standard for defining and describing RESTful APIs. Learn more about OpenAPI 3.0 here: www.slideshare.net/smartbear_...
Get started with OpenAPI 3.0 in SwaggerHub for free: swaggerhub.com/
The next version of the OAS - version 3.0 - is officially released, and comes with a host of rich, expressive capabilities for your API design and documentation. Some of these capabilities include support for describing callbacks, links to express relationships between operations, enhanced examples, and a simplified structure.
In this free SwaggerHub training, we look at what’s new in OAS 3.0, and show a live demo of defining APIs using OAS 3.0 in SwaggerHub.
We will cover:
• What’s new in OpenAPI 3.0?
• Transitioning from Swagger 2.0 to OAS 3.0
• Designing an API using OAS 3.0 on SwaggerHub
• Collaborative approach to API design and documentation with OAS 3.0 in SwaggerHub
Subscribe to all SmartBear videos here: ruclips.net/user/smartbea... 
Наука
Thank you all for the amazing feedback! We really appreciate it!
Well explained man!
Amazing explanation!
why have a fake accent ? were you born in US?
Love the way it was explained. Straightforward. No flowering words. Direct to the point. Appreciated much.
That's how one should explain things, awesome and conceptually clear.
The time is approximate
01:17 Why ?
04:20 Solution
05:28 What is OpenAPI and what is swagger
06:09 What is new on OAPI 3
06:51 Specification restructure and improve usability
-- 08:10 Parameters
-- 09:11 Contact negotiation
09:37 Demo
-- 09:37 Overview
-- 10:21 Planning
-- 11:10 How they going to build it ( tools)
-- 12:10 How to create API in swagger hub
50:17 Resources and Q/A
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.
This is just what I needed to learn how to create an API spec. Straight to the point. Thank you!
Very clear and up to the point. Just shows how documentation is SO important
A rare gem. Thank you sir!
Thank you for explaining this so well! Needed it.
Nice ! Short,crisp and clear
A few years ago, I check the date on a post, the number of views and comments to watch a video on youtube (If it has a long date, fewer views, likes, and comments, GONE!). But with time I have come to realize some videos are just not meant for everyone. But this video, GREAT ✌🏽
Great tutorial. Loved it. Got a better understating of OpenAPI from this 1h video rather than reading for hours some course-tutorial. Like!
Well structured, great explanation, and excellent example! Saves time reading myriads of documentations.
Very nice and detail presentation ...!!! GOOD Job Keshav
Simply cool. It certainly gives a jump start to API Development especially with 3.0. Thanks!
Awesome explanation!!! Thank you so much and shout out to the swagger team ;)
Thank you for this excellent video.
Thanks Keshav, very nicely done...
Very cool introduction to the subject matter. Thanks a lot for the video
Great video! All the best
Thank you so much!
Thank you soo much...I created my first API by watching this video...this is really helpful...
Thanks , very clear explanation
Thank you very much for sharing this knowledge. Appreciated!
Keshav neenga vera level boss.
Blessed tutor. Thanks!
Great intro, thank you.
Good presentation. The only weird thing is that you post the employ ID on Post trigger. But thanks for the video.
Excellent tutorial for the beginners...
extremly helpful!
Excellent presentation. Hats off !!! Just one thing , it is possible to provide sample request and response rather than defining object and array ?
Good presentation. Thanks.
Very clear, thank you.
Great explanation :)
great explanation with practical point of view.
Clear explanation. Thanks 🙏
Well explained !!
thank you Keshav..
Well explained..... Thanks for sharing wonderful knowledge
Thanks for the video, so helpful in starting out! I do have a question though, when you create and use your $ref, why are you not getting an error that there is a sibling value (in your case type) alongside your $ref?
What would be the best way to handle this? Thank you again, awesome stuff!
Hey, I know I'm late but the solution is to put the "type: object" in the "Employee" inside components, right under description, just like he did for "Employees" where "type: array" is there.
Then erase "type: object" from the rest of the code.
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?
Great presentation. Is there one for advanced modeling too?
I"ve generated petstore api using the openapi generator but can anyone explain how to write the code implementation of it by using json/yaml format? it is only creating the interfaces and controller classes which returns http response as not implemented.(I'm using springboot)
It was really a great introduction.
Thank you so much
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.
Hi, I started doing this tutorial, but after I created OPEN API I got a problem: "Note: "Try it out" is disabled because no servers are specified in the "servers" array. Please see: info on OAS3 servers".
How to resolve it?
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..
Nice demo
Excellent video
Nicely explained..!!
Great video :)
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?
That's good. Following your exact steps, I am getting these errors :
Schema error at paths['/employees'].post.requestBody
should have required property '$ref'
missingProperty: $ref
Jump to line 65
Schema error at paths['/employees'].post.requestBody
should match exactly one schema in oneOf
Jump to line 65
Schema error at paths['/employees'].post.requestBody.content['application/json']
should be object
Jump to line 67
Schema error at paths['/employees'].post.requestBody.content['schema']
should NOT have additional properties
additionalProperty: type, properties
Jump to line 69
very good video but It honestly had me wishing there was a 5x speed on youtube
amazing content friend
Excellent presentation. I have one question, how do you know what words write? where can i find the glossary o list of words allowed? I'm new designing API with swagger
Thank you! This tutorial will help you with writing OAS definitions: app.swaggerhub.com/help/tutorials/openapi-3-tutorial
how to handle the situation of multiple path parameters
I want use servers , currently we have 4 env. and I want to execute few api based on 1 server, few api on other server. Can I do this using openapi 3.0.0
Excellent
Quite descriptive
You don' mention where you are getting the names and level of all fields you are typing.
Could you please share how to create error schema for http error codes
how to connect this API to a oracle database and how can we manipulate the data in oracle database through this API designed.
Is they are any way to hide Schema/Models from API Documentation in SwaggerHub?
Do you have a product like swagger which generates OAS 3.0 specifications
Hi Narendra! Yes we do. You can check out Swagger Inspector here: swagger.io/swagger-inspector/
I am getting a warning "Sibling values are not allowed alongside $refs" after adding the reference to Employee model. Any idea why?
I got this too, after some playing about, and commenting out type: object it seemed to get rid of the compilation warning. However, I haven't got to the end of the video as yet, so don't know if this will have any other knock on effect...
200:
description: Successful user info retrieved
content:
application/json:
schema:
# type: object
$ref: '#/components/schemas/Users'
How I can secure the nodejs generated stub
Can anyone help to understand how to test the OpenAPI?
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?
Buen vídeo , pero hubieras probado el api en swagger
can we hide parameters from the UI?
Your demo was great, why? first you showed in action. and second you explained clearly what we can do. only limited by our imagination.
can u share best practices of openAPI Specification
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
How to define same api resource for multiple roles for example register api for user role normal_user, custom_user, admin and so on? could you please let me know?
The components section of the specification can be referenced multiple times swagger.io/docs/specification/using-ref/. Swaggerhub takes this to the next level by storing these reusable assets in a separate file, allowing them to be used across multiple APIs app.swaggerhub.com/help/domains/index. I hope this helps!
Thanks for your reply. but both the links that you have shared with me not working. so could you please let me know how to do that?
Here you go, let me know if these do not work for you: swagger.io/docs/specification/using-ref/ & app.swaggerhub.com/help/domains/index
The question is, why I need OpenAPI 3.0 ? Cause every company have own requirements.
Next question is, how to use it OFFLINE ?
"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 impossible to open this video fullscreen on the swagger.io site. Couldn't right click. Couldn't click anywhere near the youtube controls. Was this on purpose?
I need to know how to implement pagination .. can anyone help me pls ?
While recording, click on "New Page" within the Instaplay Recorder.
You can implement pagination using linking. Learn more here swagger.io/docs/specification/links/
At 36:00 I don't think this is the type of parameter you want to put in a path. An employee ID is a great example of a query parameter; not something from which you want to build a unique endpoint with. A path parameter would contain values like "evaluations," "taxDocuments," insuranceElections," "projectHistory..." These are things that define entire subsets of data about their parent.
what if you were building a portal for employees where they can view tasks assigned, store personal documents, view & update their personal details. All of that would fall under an employee entity
@@mcdonaldslover52 Indeed, I'm not sure I agree with my past opinion on this anymore.
Preview window shows: "We're sorry, but an error occured in this component. Please check the console for details."
31:05
Bro, why you generating swagger docs by hand?
How else can he generate if implementation does not exist yet?
@@koraytugay Spend time on the implementation, then auto-generate the swagger docs using a framework, otherwise just time wasting.
What's the usual best practice alternative to craeating swagger docs by hand?
@@design7054 I use FastAPI for Python and Swashbuckle for .net core, they both autogenerates auto-generates the swagger docs for me. I've never needed to hand-code swagger docs.
33:42 because you are using Windows LOL
test
test
test
okay my name is Rajeet and now we will talk about a shitty pee pee request
An Indian and an American I think!!