Data & schema semantics · Naming & aliasing

x-shortName

`x-shortName` appears in the document. Its value is a string. Used by 40 providers across 40 OpenAPI documents. Observed values include `Products`, `Accounts`, `Account Balances`, `Transactions`. Consistent with naming & aliasing — 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.

280 occurrences

40 documents

40 providers

purpose-named

Where it appears

Location in the document	Occurrences
other	280

What its value looks like

Value shape	Occurrences
string	280

Observed values

Sampled from the specifications, most frequent first.

ProductsAccountsAccount BalancesTransactionsDirect DebitsScheduled PaymentsPayees

Providers publishing it

All 40.

alex-bank amp-bank anz australian-military-bank auswide-bank bank-first bank-of-queensland bank-of-sydney bank-of-us banksa bankwest bcu-bank bendigo-and-adelaide-bank beyond-bank defence-bank gateway-bank gc-mutual-bank great-southern-bank greater-bank hsbc-australia hume-bank imb-bank ing-australia judo-bank macquarie-bank mystate-bank national-australia-bank newcastle-permanent people-first-bank pn-bank police-bank qudos-bank rabobank-australia racq-bank regional-australia-bank suncorp-bank teachers-mutual-bank ubank unity-bank westpac

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.