Data & schema semantics

x-description-4

`x-description-4` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `Bad username or password.`, `The connection with id {connection_id} does not exist.`, `Passwordless connection cannot be made as delivery method (sms/text) is not supp`, `The Azure AD common endpoint cannot be enabled for this connection when SCIM is `. 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.
19 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
response 19

What its value looks like

Value shapeOccurrences
string19

Observed values

Sampled from the specifications, most frequent first.

Bad username or password.The connection with id {connection_id} does not exist.Passwordless connection cannot be made as delivery method (sms/text) is not suppThe Azure AD common endpoint cannot be enabled for this connection when SCIM is The connection cannot be synchronized because setup is incomplete. Please compleThe Google Workspace Users API is not enabled on the connection. Select the EnabInvalid request query string. The message will vary depending on the cause.SCIM cannot be enabled for this connection when the Azure AD common endpoint is

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.