For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Overview
    • What is an API definition?
    • Project structure
      • Overview
      • Overlays
      • Overrides
      • Authentication
      • Servers
      • Sync your specification
        • Overview
        • API version
        • Audiences
        • Availability
        • Base path
        • Default values
        • Enum descriptions, names, and availability
        • Request + response examples
        • API Explorer control
        • Global headers
        • Ignoring elements
        • SDK method names
        • SDK variables
        • Tag display names
        • Parameter names
        • Property names
        • Idempotency
        • Pagination
        • Retry behavior
        • Schema names
        • Server names and URL templating
      • generators.yml reference
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
OpenAPIExtensions

Tag display names

||View as Markdown|
Was this page helpful?
Edit this page
Previous

SDK variables

Next

Customize parameter names

By default, tag names from your OpenAPI specification become section names in your API Reference. Use the x-displayName extension to control how these section names display in your generated documentation. This is helpful for controlling capitalization and creating user-friendly names.

Define tags with display names at the root level of your OpenAPI specification, then reference them by name in your operations:

openapi.yml
1openapi: 3.0.0
2info:
3 title: Plant Care API
4 version: 1.0.0
5
6tags:
7 - name: plant
8 x-displayName: Plants
9 description: Operations for managing plants
10 - name: watering-schedule
11 x-displayName: Watering Schedules
12 description: Handle watering schedule operations
13
14paths:
15 /plants:
16 get:
17 tags:
18 - plant
19 summary: List all plants
20 /plants/{plantId}:
21 get:
22 tags:
23 - plant
24 summary: Get a plant by ID
25 /watering-schedules:
26 get:
27 tags:
28 - watering-schedule
29 summary: List watering schedules

You can also set display names in an overrides file.

Alternatively, you can rename sections directly in your docs.yml file.