Data & schema semantics

x-possible-values

`x-possible-values` appears on schema objects and properties. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `DD-MM-YYYY`, `[''A-Z'', ''0-9'']`, `Max 100`, `Min – 0(%) \n Max – 100(%)`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
58 occurrences
3 documents
3 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 58

What its value looks like

Value shapeOccurrences
array2
string56

Observed values

Sampled from the specifications, most frequent first.

DD-MM-YYYY[''A-Z'', ''0-9'']Max 100Min – 0(%) \n Max – 100(%)[''png'', ''jpeg'', ''jpg'', ''gif'', ''pdf''][''CreditCard'',''DebitCard'',''NetBanking'',''XpressAccount'']A-Z, Space[''CreditCard'',''DebitCard'',''Netbanking'',''XpressAccount'']

Providers publishing it

All 3.

kpnpaymatevonage

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 data & schema semantics job.