You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configure/content-set/api-explorer.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,3 +112,34 @@ The API Explorer generates the following types of pages from your OpenAPI spec:
112
112
- **Landing page**: An overview of the API grouped by tag
113
113
- **Operation pages**: One page per API operation, with the HTTP method, path, parameters, request body, response schemas, and examples
114
114
- **Schema type pages**: Dedicated pages for complex shared types such as `QueryContainer` and `AggregationContainer`
115
+
116
+
## OpenAPI extensions
117
+
118
+
The API Explorer supports the following OpenAPI specification extensions to enhance navigation and display:
119
+
120
+
### `x-displayName` for tags
121
+
122
+
Use the `x-displayName` extension on tag objects to provide user-friendly display names in navigation and landing pages while maintaining stable URLs based on the canonical tag name.
123
+
124
+
```json
125
+
{
126
+
"tags": [
127
+
{
128
+
"name": "tasks",
129
+
"description": "The task management APIs enable you to get information about tasks currently running.",
- When `x-displayName` is present, it's used for navigation titles and section headings in the API Explorer
143
+
- When `x-displayName` is absent, the canonical tag `name` is used as a fallback
144
+
- Navigation URLs and internal references always use the canonical tag `name` for stability
145
+
- This extension follows the [Redocly specification extension pattern](https://redocly.com/docs-legacy/api-reference-docs/specification-extensions/x-display-name)
0 commit comments