/organizations/{org_id}/vpc/region/{region_id}/vpc_endpoints/{vpc_endpoint_id}Retrieve VPC endpoint details
Retrieves the current state and configuration details of a specified VPC endpoint.
Quick start
curl "https://console.neon.tech/api/v2/organizations/$ORG_ID/vpc/region/$REGION_ID/vpc_endpoints/$VPC_ENDPOINT_ID" \
-H "Authorization: Bearer $NEON_API_KEY"Every field below is optional. An empty body works too.
neon vpc endpoint status <vpc_endpoint_id> --org-id <id> --region-id <region_id> --region-id <region-id>Parameters
org_idThe Neon organization ID
region_idThe Neon region ID. Azure regions are currently not supported.
vpc_endpoint_idThe VPC endpoint ID
Response
200Returned the current status and configuration details of the specified VPC endpoint.
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.