Events
34 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
34 extensions
10675 occurrences
9 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
| x-stream-index | `x-stream-index` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `001`, `002`, `003`, `004`. Consistent w | 9761 | 1 |
| x-events | `x-events` appears on operations. It is used as a marker with no value. Used by 2 providers across 4 OpenAPI documents. Consistent with events — this is inferred from where the key appears and what it | 290 | 2 |
| x-stream-docs-page-id | `x-stream-docs-page-id` appears on schema objects and properties. Its value is a string. Used by a single provider across 4 OpenAPI documents. Observed values include `pinned_messages`, `threads`, `th | 133 | 1 |
| x-webhook-equivalent | `x-webhook-equivalent` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `webhook-timestamp`, `webhook-signature`. Consistent w | 132 | 1 |
| x-min-subscription | `x-min-subscription` appears on path items. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `standard`, `value`, `professional`, `free`. Consistent | 66 | 1 |
|
x-apideck-event-type
vendor |
`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 t | 56 | 1 |
| x-webhooks | `x-webhooks` appears at the root of the document. Its value is a structured object. Used by 20 providers across 54 OpenAPI documents. Consistent with events — this is inferred from where the key appea | 54 | 20 |
|
x-ibm-events
vendor |
`x-ibm-events` appears on operations. Its value is a structured object. Used by a single provider across 5 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm toolin | 29 | 1 |
| x-envoy-upstream-service-time | `x-envoy-upstream-service-time` appears on header objects. Its value is a string. Used by 2 providers across 10 OpenAPI documents. Observed values include `91`. Consistent with events — this is inferr | 26 | 2 |
| x-stream-filter-fields | `x-stream-filter-fields` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 4 OpenAPI documents. Consistent with events — this is inferred fro | 22 | 1 |
| x-stream-map | `x-stream-map` appears on schema objects and properties. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with events — this is inferred from where th | 21 | 1 |
| x-event-type | `x-event-type` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `sync.complete`, `sync.paused`, `connection.created`, `connect | 18 | 1 |
|
x-speakeasy-sse-sentinel
vendor |
`x-speakeasy-sse-sentinel` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-speakeasy-` namespace, so its meaning is defined b | 10 | 1 |
| x-stream-sort-combinations | `x-stream-sort-combinations` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with events — this is inferred from where t | 9 | 1 |
| x-stream-sort-fields | `x-stream-sort-fields` appears on schema objects and properties. Its value is a list. Used by a single provider across 3 OpenAPI documents. Consistent with events — this is inferred from where the key | 8 | 1 |
| x-websocket | `x-websocket` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the key appears and what it | 7 | 1 |
| x-downstream-splat-expressions | `x-downstream-splat-expressions` appears in the document. Its value is a list. Used by a single provider across 5 OpenAPI documents. Consistent with events — this is inferred from where the key appear | 5 | 1 |
|
x-ms-workflow-subscription-capacity
vendor |
`x-ms-workflow-subscription-capacity` appears on header objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined | 4 | 1 |
|
x-ms-workflow-subscription-id
vendor |
`x-ms-workflow-subscription-id` appears on header objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined by ms | 4 | 1 |
|
x-amz-meta-callback_domain
vendor |
`x-amz-meta-callback_domain` appears on schema objects and properties and on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-amz-` names | 2 | 1 |
|
x-amz-meta-callback_url
vendor |
`x-amz-meta-callback_url` appears on schema objects and properties and on response objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-amz | 2 | 1 |
|
x-ms-qps-subscribed
vendor |
`x-ms-qps-subscribed` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined by m | 2 | 1 |
| x-upstream-documentation | `x-upstream-documentation` appears in the info block. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `https://developer.wordpress.org/rest-api/`. Consis | 2 | 2 |
| x-webhook-delivery | `x-webhook-delivery` appears on operations. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with events — this is inferred from where the key appears | 2 | 1 |
| x-callback-request | `x-callback-request` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the key appears and w | 1 | 1 |
| x-disable-subscription | `x-disable-subscription` appears at the root of the document. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `off`. Consistent with events — this i | 1 | 1 |
| x-error-events | `x-error-events` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the ke | 1 | 1 |
| x-published-event-operations | `x-published-event-operations` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the ke | 1 | 1 |
|
x-speakeasy-webhooks
vendor |
`x-speakeasy-webhooks` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-speakeasy-` namespace, so its meani | 1 | 1 |
| x-subscriptions-contact | `x-subscriptions-contact` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the key | 1 | 1 |
| x-upstream-info | `x-upstream-info` appears in the info block. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the key appears | 1 | 1 |
| x-upstream-project | `x-upstream-project` appears at the root of the document. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `https://github.com/atfweb/regulations-cor | 1 | 1 |
| x-upstream-spec | `x-upstream-spec` appears in the info block. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `https://github.com/inveniosoftware/invenio-openapi`. C | 1 | 1 |
| x-websocket-api | `x-websocket-api` appears at the root of the document. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with events — this is inferred from where the k | 1 | 1 |