Update magic link plugin configuration
API Reference / Authentication / Update magic link plugin configuration
PATCH /projects//branches//auth/plugins/magic-link
Section titled “PATCH /projects//branches//auth/plugins/magic-link”Updates the magic link plugin configuration for Neon Auth. The magic link plugin enables passwordless authentication via email magic links.
Parameters
Section titled “Parameters”project_id(string, path, required) The Neon project IDbranch_id(string, path, required) The Neon branch ID
Request body
Section titled “Request body”enabled(boolean, optional) Whether to enable the magic link plugin.expires_in(integer, optional, format: int32) Minutes until the magic link expires.disable_sign_up(boolean, optional) When true, sign-up via magic link is disabled.
Response (200)
Section titled “Response (200)”{
"enabled": true,
"expires_in": 5,
"disable_sign_up": false
}Code examples
Section titled “Code examples”curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/branches/$BRANCH_ID/auth/plugins/magic-link" \
-X PATCH \
-H "Authorization: Bearer $NEON_API_KEY"import { createNeonClient, raw } from '@neon/sdk';
const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.updateNeonAuthMagicLinkPlugin({
client: neon.client,
path: {
project_id: process.env.PROJECT_ID,
branch_id: process.env.BRANCH_ID
}
});Console
Section titled “Console”Console path: Projects → Auth → Plugins
Errors
Section titled “Errors”default General 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.
-
request_id(string, optional) Unique identifier for the request, useful for debugging. You can set this value manually by including anX-Request-IDheader in the request. If not provided, the value will be generated automatically. -
code(string, required) Machine-readable code classifying the error type. Seemessagefor a human-readable explanation. Default: `` -
message(string, required) Error message