AsyncAPI channel · Okta · Okta Event Hooks and Log Streams

okta/event-hook/verification

One-time verification handshake. After an Event Hook is created (or its endpoint URL changes), Okta sends a single HTTP GET request to the registered endpoint with an `x-okta-verification-challenge` header. The endpoint must echo the header value back in a JSON body under the property `verification`. The Event Hook's `verificationStatus` transitions from `UNVERIFIED` to `VERIFIED` on success. `UNV

Open source AsyncAPI → All Okta channels Okta provider profile
Provider: Okta AsyncAPI: v2.6.0 Spec: Okta Event Hooks and Log Streams Operations: 2 Messages: 2

Channel address

okta/event-hook/verification

Operations

publish
respondEventHookVerification
Echo the challenge value in a JSON body to complete verification.
receiveEventHookVerification
Receive the one-time verification GET from Okta.

Messages

EventHookVerificationResponse
JSON body the endpoint must return to complete verification — a single property `verification` containing the value of the `x-okta-verification-challenge` header from the GET request.
Content-Type: application/json
EventHookVerificationChallenge
The single GET request Okta sends to confirm endpoint ownership. The challenge value is in the `x-okta-verification-challenge` header; no request body is sent.
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.