Mocking & testing

x-example-php

`x-example-php` appears on parameter objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `"00000000-0000-0000-0000-000000000000"`, `"INV-001", "INV-002"`, `Status=="' . \XeroAPI\XeroPHP\Models\Accounting\Account::STATUS_ACTIVE`, `Status=="' . XeroAPI\XeroPHP\Models\Accounting\BatchPayment::STATUS_AU`. 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.
26 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
parameter 26

What its value looks like

Value shapeOccurrences
string26

Observed values

Sampled from the specifications, most frequent first.

"00000000-0000-0000-0000-000000000000""INV-001", "INV-002"Status=="' . \XeroAPI\XeroPHP\Models\Accounting\Account::STATUS_ACTIVEStatus=="' . XeroAPI\XeroPHP\Models\Accounting\BatchPayment::STATUS_AUStatus=="' . XeroAPI\XeroPHP\Models\Accounting\BankTransaction::STATUSContactStatus=="' . \XeroAPI\XeroPHP\Models\Accounting\Contact::CONTACStatus=="' . \XeroAPI\XeroPHP\Models\Accounting\ContactGroup::STATUS_AStatus=="' . \XeroAPI\XeroPHP\Models\Accounting\CreditNote::STATUS_DRA

Providers publishing it

All 1.

xero

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.