Mocking & testing

x-examples

`x-examples` appears on schema objects and properties. Its value is a structured object. Used by 51 providers across 158 OpenAPI documents. Consistent with mocking & testing — this is inferred from where the key appears and what it carries, not from any published definition.

Mocking & testing 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.

1178 occurrences

158 documents

51 providers

purpose-named

Where it appears

Location in the document	Occurrences
schema	793
components	2
response	234
requestBody	75
parameter	61
operation	13

What its value looks like

Value shape	Occurrences
object	962
array	2
empty	211
string	3

Observed values

Sampled from the specifications, most frequent first.

nullPOST /20160918/externalcontainerdatabases/<externalContainerDatabaseId&g

Providers publishing it

Showing 50 of 51.

activefence adafruit-io alpaca amadeus amadeus-traveler-media appdirect autodesk-fusion aviationweather axlehire bigcommerce elastic-path ev-energy factset finix finix-payments frankieone kuma leapsome lianlian-global lucidya-ltd mailmodo mediamath microsoft-azure noaa nuclei octo openchargemap oracle padlet pagerduty palo-alto-networks plaid projectdiscovery punchh seldon sendcloud sendgrid sendhub small-improvements smarty smtp2go spree spree-commerce timecamp trustlayer veho vendasta vessel visa yousign

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 mocking & testing job.