Data & schema semantics · Identity & relationships

x-workday-operation-id

`x-workday-operation-id` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-workday-` namespace, so its meaning is defined by workday tooling rather than by OpenAPI. Observed values include `a06e49cf714e100007fd676f0d2c0101`, `a7a41b4d029c10000a8fc88465fc18ee`, `ce00e3198c5b10000770878cd8ce0000`, `01bedd7c1f9e10001e0a6dc620fd00ea`. Consistent with identity & relationships — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-workday- 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.
20 occurrences
1 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 20

What its value looks like

Value shapeOccurrences
string20

Observed values

Sampled from the specifications, most frequent first.

a06e49cf714e100007fd676f0d2c0101a7a41b4d029c10000a8fc88465fc18eece00e3198c5b10000770878cd8ce000001bedd7c1f9e10001e0a6dc620fd00ea3544fcea278410000df2353044890000bd578ca9ac80100018873fe30bdd00000277c526ae0f100007e0388a188612a2569364e930c1100015f17cf6454f0000

Providers publishing it

All 1.

workday-business-processes

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.