Data & schema semantics · Type system

x-enum-varnames

`x-enum-varnames` appears on schema objects and properties. Its value is a list. Used by 75 providers across 124 OpenAPI documents. Observed values include `[INPUT, FILTER, PRE_OUTPUT, OUTPUT]`, `['UserFilterSelf']`, `['TradeTakerSideYes', 'TradeTakerSideNo']`, `['TradeTakerOutcomeSideYes', 'TradeTakerOutcomeSideNo']`. Consistent with type system — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
1585 occurrences
124 documents
75 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 1557
parameter 5
operation 23

What its value looks like

Value shapeOccurrences
array1585

Observed values

Sampled from the specifications, most frequent first.

[INPUT, FILTER, PRE_OUTPUT, OUTPUT]['UserFilterSelf']['TradeTakerSideYes', 'TradeTakerSideNo']['TradeTakerOutcomeSideYes', 'TradeTakerOutcomeSideNo']

Providers publishing it

Showing 50 of 75.

aerisagorapulseairmdralayacarealgoliaaltranchoragearcadearcade-devavayaaxelarbabylon-labsbenzingabirdblues-wirelesscalyptiacisco-crossworkconta-azulconvoydatadogdatadog-apmdaytona-iodropboxe2b-deveonequinixflume-healthfoliogradlegreen-screens-aigroundtruthharnesshellosignjp-morgan-chasekalshikeboolakongleapliberty-globallightspeedlinelocalaimeowmomentmrscrapernetdataobservepointocean-ioocean-securitypagopa

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 data & schema semantics job.