Data & schema semantics · Type system

x-apideck-enum-id

`x-apideck-enum-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. It sits in the `x-apideck-` namespace, so its meaning is defined by apideck tooling rather than by OpenAPI. Observed values include `sort_direction`, `unified_api`, `bank_accounts.account_type`, `addresses.type`. Consistent with type system — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-apideck- namespace 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.
159 occurrences
4 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 159

What its value looks like

Value shapeOccurrences
string159

Observed values

Sampled from the specifications, most frequent first.

sort_directionunified_apibank_accounts.account_typeaddresses.typebank-accounts.account_typecurrenciesemails.typephone_numbers.type

Providers publishing it

All 1.

apideck

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.