AsyncAPI channel · RudderStack · RudderStack Event Streaming API

/v1/webhook

Webhook Source endpoint. Accepts inbound webhooks from third-party SaaS tools. RudderStack identifies which Webhook Source should handle the request using the write key supplied via Basic Auth, then normalizes the raw payload (application/json, application/x-www-form-urlencoded, or multipart/form-data) into a RudderStack event for downstream routing.

Open source AsyncAPI → All RudderStack channels RudderStack provider profile
Provider: RudderStack AsyncAPI: v2.6.0 Spec: RudderStack Event Streaming API Operations: 1 Messages: 1

Channel address

/v1/webhook

Operations

receiveWebhookSourceEvent
Receive an inbound webhook from a third-party SaaS source. RudderStack accepts both POST and GET on this path; the handler is the same.

Messages

InboundWebhookPayload
Raw inbound webhook payload received from a third-party SaaS source. RudderStack converts the payload (JSON, form-urlencoded, or multipart) into one or more RudderStack events using the source's Webho
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.