📄️ Info
screenshot from swagger website
📄️ Servers
screenshot from swagger website
📄️ Tags
screenshot from swagger website
📄️ Paths
The paths section defines individual endpoints (paths) in your API, and the HTTP methods (operations) supported by these endpoints
📄️ Components
Often, multiple API operations have some common parameters or return the same response structure. To avoid code duplication, you can place the common definitions in the global components section and reference them using $ref. In the example below, duplicate definitions of a User object are replaced with a single component and references to that component.
📄️ Externally Defined Components
from API
📄️ Security
Bearer Authentication
📄️ Parameters
Operations can have parameters passed via URL path (/users/), query string (/users?role=admin), headers (X-CustomHeader debug=0). You can define the parameter data types, format, whether they are required or optional, and other details
📄️ Link
Defining Links
📄️ Media Type
Media type is a format of a request or response body data. Web service operations can accept and return data in different formats, the most common being JSON, XML and images. You specify the media type in request and response definitions. Here is an example of a response definition.