Migrating to OpenAPI 3.0: How to Convert Your Existing APIs with Swagger Tools

The OpenAPI Specification specifies the rules and syntax required to describe the API’s interface. The OAS has evolved to meet the needs of modern API teams and continues to introduce updates to make the specification simpler to use, and easier for humans and computers to understand.

While everyone wants to take advantage OAS 3.0, it can get tricky when you want to do so for an existing API. You may have APIs defined in Swagger 2.0 that you want to migrate to OAS 3.0, or maybe you have a backload of legacy APIs that don’t yet a definition in place.

Here’s what you’ll be learning:
• What’s new in OAS 3.0
• How to generate OAS 3.0 definitions through code annotations using the SwaggerHub open source Maven plugin
• How to generate OAS 3.0 definitions from API end points using Swagger Inspector
• How to convert Swagger 2.0 definitions to OAS 3.0 definitions using SwaggerHub
• How to create consumer-friendly APIs using OAS 3.0 and SwaggerHub

[deepgandhi]

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?

[asherazeem]

Bro could you tell me what is 403 error. I have searched on the bundle of place but I could not find a proper answer.