Mocking & testing

x-examples

`x-examples` appears on schema objects and properties and on response objects. Its value is a structured object. Used by 98 providers across 308 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.

2779 occurrences

308 documents

98 providers

purpose-named

Where it appears

Location in the document	Occurrences
response	754
requestBody	266
schema	1581
components	20
parameter	122
operation	36

What its value looks like

Value shape	Occurrences
object	2331
array	134
empty	308
string	6

Observed values

Sampled from the specifications, most frequent first.

nullPOST /20160918/externalcontainerdatabases/<externalContainerDatabaseId&g

Providers publishing it

Showing 50 of 98.

accredify0604 activefence adafruit-io aftership alpaca amadeus amadeus-traveler-media apollo-insurance appdirect assignar autodesk-fusion aviationweather axlehire bigcommerce billdesk bond cart-com centrapay cloudchipr dealhub deluxe demandbase doorloop eagle-eye-networks elastic-path eliq emarsys entur ev-energy factset fda-regulations finix finix-payments fixflo frankieone furiosa gumlet harness infoworks jp-morgan-chase karmacheck kontaktio kuma leapsome lianlian-global lucidya-ltd magic-moment mailmodo mapp mediamath

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.