/projects/{project_id}/branches/{branch_id}/auth/allow_localhostUpdate localhost allow setting
Updates the localhost allow setting for the specified branch's Neon Auth integration.
When enabled, authentication flows work from localhost without adding it to the redirect URI whitelist.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/branches/$BRANCH_ID/auth/allow_localhost" \
-X PATCH \
-H "Authorization: Bearer $NEON_API_KEY"# enable
neon neon-auth domain allow-localhost enable
# disable
neon neon-auth domain allow-localhost disableParameters
project_idThe Neon project ID
branch_idThe Neon branch ID
Request body
1 required Required: allow_localhost.
allow_localhostWhether to allow localhost connections
Response
200Updated the allow localhost configuration
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.