Events

x-apideck-event-type

`x-apideck-event-type` appears on operations. 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 `accounting.customer.created`, `accounting.customer.updated`, `accounting.customer.deleted`, `accounting.invoice.created`. Consistent with events — this is inferred from where the key appears and what it carries, not from any published definition.

Events 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.
56 occurrences
4 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 56

What its value looks like

Value shapeOccurrences
string56

Observed values

Sampled from the specifications, most frequent first.

accounting.customer.createdaccounting.customer.updatedaccounting.customer.deletedaccounting.invoice.createdaccounting.invoice.updatedaccounting.invoice.deletedaccounting.invoice_item.createdaccounting.invoice_item.updated

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 events job.