Skip to main content
Neon Postgres Docs

Search documentation

Type to search this documentation.

Update Neon Auth webhook configuration

PUT/projects/{project_id}/branches/{branch_id}/auth/webhooksUpdate Neon Auth webhook configuration

Updates the webhook configuration for the specified branch's Neon Auth integration. Webhooks notify an external endpoint when auth events occur, such as user creation or sign-in.

Parameters

project_idstringpathrequired

The Neon project ID

pattern ^[a-z0-9-]{1,60}$

branch_idstringpathrequired

The Neon branch ID

pattern ^[a-z0-9-]{1,60}$

Request body

required
application/json
objectNeonAuthWebhookConfig
enabledbooleanrequired

Whether the webhook is active.

enabled_eventsarray of string

Event types that trigger this webhook. Covers user lifecycle, email/OTP delivery, organization invitations, and phone verification events; see the enum for exact values.

Show child attributes
timeout_secondsinteger

Maximum time, in seconds, to wait for a response from the webhook endpoint.

default 5 · maximum 10 · minimum 1

webhook_urlstring

Destination URL that receives webhook event payloads.

Example request
{
  "enabled": true,
  "enabled_events": [
    "organization.invitation.accepted"
  ],
  "timeout_seconds": 5,
  "webhook_url": "string"
}

Responses

200Returns the updated webhook configurationapplication/json
objectNeonAuthWebhookConfig
enabledbooleanrequired

Whether the webhook is active.

enabled_eventsarray of string

Event types that trigger this webhook. Covers user lifecycle, email/OTP delivery, organization invitations, and phone verification events; see the enum for exact values.

Show child attributes
timeout_secondsinteger

Maximum time, in seconds, to wait for a response from the webhook endpoint.

default 5 · maximum 10 · minimum 1

webhook_urlstring

Destination URL that receives webhook event payloads.

Example response
{
  "enabled": true,
  "enabled_events": [
    "organization.invitation.accepted"
  ],
  "timeout_seconds": 5,
  "webhook_url": "string"
}
defaultGeneral Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu