Skip to main content
Neon Postgres Docs

Search documentation

Type to search this documentation.

List VPC endpoint restrictions

GET/projects/{project_id}/vpc_endpointsList VPC endpoint restrictions

Lists VPC endpoint restrictions for the specified Neon project.

Parameters

project_idstringpathrequired

The Neon project ID

pattern ^[a-z0-9-]{1,60}$

Responses

200Returned VPC endpoint restrictions for the specified projectapplication/json
objectVPCEndpointsResponse
endpointsarray of objectrequired

List of VPC endpoints returned by the request.

Show child attributes
Show array items
labelstringrequired

A descriptive label for the VPC endpoint

vpc_endpoint_idstringrequired

Cloud provider identifier for the VPC endpoint.

Example response
{
  "endpoints": [
    {
      "label": "string",
      "vpc_endpoint_id": "string"
    }
  ]
}
defaultGeneral 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. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu