Data & schema semantics

x-description-7

`x-description-7` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `The client does not exist`, `The action_id field value cannot be empty, null or undefined`, `options.set_user_root_attributes can be set only for enterprise connections, soc`, `The Google Workspace Groups API is not enabled on the connection. Select the Ena`. 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.
9 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
response 9

What its value looks like

Value shapeOccurrences
string9

Observed values

Sampled from the specifications, most frequent first.

The client does not existThe action_id field value cannot be empty, null or undefinedoptions.set_user_root_attributes can be set only for enterprise connections, socThe Google Workspace Groups API is not enabled on the connection. Select the EnaPayload validation error: ''String does not match pattern ^con_[A-Za-z0-9]{16}$'The organization does not existCannot update username and email_verified simultaneously.JWT (link_with) contains an invalid sub claim.

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.