Mocking & testing

x-example

`x-example` appears on operations and on schema objects and properties. Its value is a string. Used by 42 providers across 235 OpenAPI documents. Observed values include `POST /20160918/autonomousDatabases/<autonomousDatabaseId>/actio`, `POST /20160918/autonomousContainerDatabases/<autonomousContainerDatabase`, `1`, `6f0bece6-7df3-4da4-af02-5e7f16e5e6fc`. 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.

6767 occurrences

235 documents

42 providers

purpose-named

Where it appears

Location in the document	Occurrences
parameter	552
schema	1793
operation	4331
path	43
securityScheme	16
header	2
response	12
requestBody	1
other	14
tag	3

What its value looks like

Value shape	Occurrences
string	6339
integer	154
object	32
number	46
boolean	45
empty	2
array	149

Observed values

Sampled from the specifications, most frequent first.

POST /20160918/autonomousDatabases/<autonomousDatabaseId>/actioPOST /20160918/autonomousContainerDatabases/<autonomousContainerDatabase16f0bece6-7df3-4da4-af02-5e7f16e5e6fc2truefalse0

Providers publishing it

All 42.

adobe-suite airbus-oneatlas akash alayacare amadeus amadeus-reservations amadeus-solutions amadeus-traveler-media angelcam avis-budget bharti-airtel bitvore box cms-gov constant-contact crossenagage docspring edmunds egym entur georgia-institute-of-technology hootsuite iab-tech-lab instana kpn logz-io lucidya-ltd mailchimp mercedes-me microsoft-azure mtn-group nginx notarize oracle oracle-cloud oracle-platforms pagopa signadot tago-io xero zero-networks zuplo

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.