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.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.