AsyncAPI channel · Keap · Keap REST Hooks

hook.verification

Verification handshake from Keap to the subscriber. Issued when a subscription is created via `POST /rest/v1/hooks` (Immediate Confirmation) or re-verified via `POST /rest/v1/hooks/{key}/verify`. The subscriber must respond with HTTP 200 and echo the `X-Hook-Secret` header back.

Provider: Keap AsyncAPI: v2.6.0 Spec: Keap REST Hooks Operations: 1 Messages: 1

Channel address

hook.verification

Operations

onHookVerification
Subscription verification request

Messages

HookVerification
Empty-body verification `POST` issued by Keap to the subscriber's `hookUrl`. The subscriber must respond with HTTP 200 and echo the `X-Hook-Secret` header value to confirm ownership of the endpoint.
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.