Data & schema semantics

x-description-5

`x-description-5` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Identity connection does not exist.`, `custom_password_hash option cannot be set because the universal password hash fe`, `The Google Workspace Users API (options.api_enable_users) cannot be disabled for`, `The Groups extended attribute is not enabled on the connection. Select the Group`. 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.
13 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
response 13

What its value looks like

Value shapeOccurrences
string13

Observed values

Sampled from the specifications, most frequent first.

Identity connection does not exist.custom_password_hash option cannot be set because the universal password hash feThe Google Workspace Users API (options.api_enable_users) cannot be disabled forThe Groups extended attribute is not enabled on the connection. Select the GroupThe connection cannot be synchronized because setup is incomplete. Please compleInvalid query string paging options. The message will vary depending on the causConnection must be a database connection.The specified connection (con_0000000000000001) is not enabled for the organizat

Providers publishing it

All 1.

auth0

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.