Documentation & DX

x-displayName

`x-displayName` appears on tags and in the document. Its value is a string. Used by 122 providers across 215 OpenAPI documents. Observed values include `Users`, `Webhooks`, `Authentication`, `Introduction`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX derived description

How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.

Also published under another name. This key exists in the wild spelled more than one way — differing only by case or a hyphen, which means no tool can treat them as the same thing: x-DisplayName. Each is catalogued separately here because that is how they exist.

3319 occurrences

215 documents

122 providers

purpose-named

Where it appears

Location in the document	Occurrences
other	1208
tag	2078
operation	24
securityScheme	9

What its value looks like

Value shape	Occurrences
string	3316
object	3

Observed values

Sampled from the specifications, most frequent first.

UsersWebhooksAuthenticationIntroductionAccountOrdersOrganizationsApplications

Providers publishing it

Showing 50 of 122.

1fort 1nce acquia affise aiven algolia angelcam appdirect asapp asapp3 atlar autoleadstar azupay bevz blockdaemon bonitasoft booking-com boxc brandfolder btcmarkets bud-co bullish citi clear-street cloudkitchens cognite convelio coveo curated-for-you devtron docker docker-hub dolby doordash drivewealth elastic-observability elk-stack encharge eon equinix eu-open-data-portal fatcat filecoin fireworks-ai frontegg gitpod gradle green-screens-ai gridx-ai growthbook

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the documentation & dx job.