Search results

Step 7: The tags object (OpenAPI tutorial)

I need your input — I'm conducting a survey about trends in developer documentation for 2020. If you write docs for developers, please take this survey. (You can view the ongoing results viewed here.)

The tags object allows you to arrange the paths (endpoints) into named groups in the Swagger UI display.

Defining tags at the root level

At the root level, the tags object lists all the tags that are used in the operation objects (which appear within the paths object, as explained in Step 4: The paths object). Here’s an example of the tags object for our OpenWeatherMap API:

  - name: Current Weather Data
    description: "Get current weather details"

We have just one tag, but you could have as many as you want (if you have a lot of endpoints, it would make sense to create multiple tags to group them). You can list both the name and a description for each tag. The description appears as a subtitle for the tag name in the Swagger UI display.

Tags at the path object level

The tags object at the root level should list all tags (groups) that you want in your API. Then in each path object under paths, you list the tag you want that path grouped under.

For example, in the operations object for the /current path, we used the tag Current Weather Data:

      - Current Weather Data

This tag is defined at the global level, so the /weather path will be grouped here.

View the Appearance in Swagger UI

Add the following to the root level of your OpenAPI document in Swagger Editor:

  - name: Current Weather Data
    description: "Get current weather details"

Observe how the description appears next to the collapsed Current Weather Data section.

Tags defined at the root level
Tags defined at the root level

All paths that have the same tag are grouped together in the display. For example, paths that have the Current Weather Data tag will be grouped together under the title Current Weather Data. Each group title is a collapsible/expandable toggle.

The order of the tags in the tags object at the root level determines their order in Swagger UI. Additionally, the descriptions appear to the right of the tag name.

In our sample OpenAPI spec, tags don’t seem all that necessary since we’re just documenting one path/endpoint. (Additionally, I configured the Swagger UI demo to expand the section by default.) But imagine if you had a robust API with 30+ paths to describe. You would certainly want to organize the paths into logical groups for users to navigate.

47% Complete

47/127 pages complete. Only 80 more pages to go.