Mocking & testing

x-example-path

`x-example-path` appears on operations. Its value is a string. Used by 2 providers across 5 OpenAPI documents. Observed values include `/webhooks/message-status`, `/webhooks/inbound-message`, `/webhooks/request-status-update`, `/webhooks/final-report`. 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.
10 occurrences
5 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 10

What its value looks like

Value shapeOccurrences
string10

Observed values

Sampled from the specifications, most frequent first.

/webhooks/message-status/webhooks/inbound-message/webhooks/request-status-update/webhooks/final-report/webhooks/inbound-sms/webhooks/events-callback

Providers publishing it

All 2.

kpnvonage

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.