Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

Send test email using the saved email provider

POST/projects/{project_id}/branches/{branch_id}/auth/email_provider/testSend test email using the saved email provider

Sends a test email using the branch's already-saved custom SMTP configuration. Only the recipient_email is provided — the stored SMTP settings and password are used server-side, so the caller does not need to re-supply (or be able to read) the password. This avoids the GET response's masked password being sent back, which would fail SMTP authentication.

Requires a configured custom SMTP provider on a Better Auth integration. A shared provider, a missing configuration, or a non-Better-Auth integration is rejected.

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
objectSendNeonAuthEmailProviderTestRequest

Request to test the branch's saved email provider. Only the recipient is supplied; the stored SMTP settings and password are used server-side.

recipient_emailstring · emailrequired

The email address to send the test email to.

maxLength 256 · minLength 1

Example request
{
  "recipient_email": "user@example.com"
}

Responses

200Response with the result of the test email sendapplication/json
objectSendNeonAuthTestEmailResponse
error_messagestring

The error message from the email server.

successbooleanrequired

Whether the test email was sent successfully.

Example response
{
  "error_message": "string",
  "success": 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