AsyncAPI channel · Okta · Okta Event Hooks and Log Streams

okta/event-hook/delivery

Event Hook delivery channel. Okta POSTs a CloudEvents 0.1-style envelope to the registered endpoint each time one of the subscribed event types fires. The body contains a `data.events` array of `LogEvent` objects — the same shape returned by the System Log API. Authentication is via a customer-chosen `Authorization` header value (the `EventHookChannelConfigAuthScheme` with `type: HEADER`).

Provider: Okta AsyncAPI: v2.6.0 Spec: Okta Event Hooks and Log Streams Operations: 1 Messages: 1

Channel address

okta/event-hook/delivery

Operations

receiveEventHookDelivery
Receive a batch of subscribed System Log events.

Messages

EventHookDelivery
CloudEvents 0.1-style envelope that Okta POSTs for every batch of subscribed System Log events. Sent with the customer's chosen `Authorization` header value and `Content-Type: application/json`.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.