/projects/{project_id}/branches/{branch_id}/auth/email_provider/testbetaSend 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.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/branches/$BRANCH_ID/auth/email_provider/test" \
-X POST \
-H "Authorization: Bearer $NEON_API_KEY"neon neon-auth config email-provider test --recipient-email <recipient-email>Parameters
project_idThe Neon project ID
branch_idThe Neon branch ID
Request body
1 required Required: recipient_email.
recipient_emailThe email address to send the test email to.
≥1 chars, ≤256 chars
Response
200Response with the result of the test email send
Errors
General error
This endpoint can return the standard Neon API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
Retry guidance
If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.
Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.
Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.