Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

Retrieve email and password configuration

GET/projects/{project_id}/branches/{branch_id}/auth/email_and_passwordRetrieve email and password configuration

Retrieves the email and password authentication configuration for the specified branch's Neon Auth integration, including whether it is enabled and the email verification method.

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}$

Responses

200Returns the email and password configuration for Neon Authapplication/json
objectNeonAuthEmailAndPasswordConfig
auto_sign_in_after_verificationbooleanrequired

Whether users are automatically signed in after verifying their email

disable_sign_upbooleanrequired

Whether to disable new user sign ups

email_verification_methodstringrequired

The email verification method to use. - `link`: Sends a verification link via email - `otp`: Sends a one-time password (OTP) via email

one of "link", "otp"

enabledbooleanrequired

Whether email and password authentication is enabled

require_email_verificationbooleanrequired

Whether email verification is required before users can sign in

send_verification_email_on_sign_inbooleanrequired

Whether to send a verification email when users sign in

send_verification_email_on_sign_upbooleanrequired

Whether to send a verification email when users sign up

Example response
{
  "auto_sign_in_after_verification": true,
  "disable_sign_up": true,
  "email_verification_method": "link",
  "enabled": true,
  "require_email_verification": true,
  "send_verification_email_on_sign_in": true,
  "send_verification_email_on_sign_up": true
}
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