AsyncAPI channel · Neon · Neon Auth Webhook Events

/webhook

Neon Auth sends webhook events to your configured endpoint as HTTP POST requests with JSON payloads. Each event includes a type field identifying the event and relevant data. Your endpoint should respond with a 2xx status code to acknowledge receipt.

Open source AsyncAPI → All Neon channels Neon provider profile
Provider: Neon AsyncAPI: v2.6.0 Spec: Neon Auth Webhook Events Operations: 1 Messages: 3

Channel address

/webhook

Operations

publish
receiveAuthWebhookEvent
Receive authentication webhook events

Messages

otpDelivery
Sent when an OTP code needs to be delivered to a user for email verification or two-factor authentication.
Content-Type: application/json
magicLinkDelivery
Sent when a magic link needs to be delivered to a user for passwordless authentication.
Content-Type: application/json
userCreated
Sent when a new user account is created through Neon Auth.
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.