/projects/{project_id}/vpc_endpoints/{vpc_endpoint_id}Set VPC endpoint restriction
Sets or updates a VPC endpoint restriction for a Neon project. When a VPC endpoint restriction is set, the project only accepts connections from the specified VPC. A VPC endpoint can be set as a restriction only after it is assigned to the parent organization of the Neon project.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/vpc_endpoints/$VPC_ENDPOINT_ID" \
-X POST \
-H "Authorization: Bearer $NEON_API_KEY"neon vpc project restrict <vpc_endpoint_id> --project-id <id>Parameters
project_idThe Neon project ID
vpc_endpoint_idThe VPC endpoint ID
Request body
1 required Required: label.
labelResponse
200Configured the specified VPC endpoint as a restriction for the specified project.
No example available.
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.