This API is used to update a VPC endpoint connection.

You can debug this API in . Automatic authentication is supported.

POST /v1.0/{project_id}/clusters/{cluster_id}/vpcepservice/connections

**Table 1** Path parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details, see Obtaining a Project ID and Name.
cluster_id	Yes	String	ID of the cluster that you want to update the VPC endpoint

**Table 2** Request body parameter
Parameter	Mandatory	Type	Description
action	Yes	String	Expected operation. receive: accept the VPC endpoint connection reject: reject the VPC endpoint connection
endpointIdList	Yes	Array of strings	VPC endpoint IDs list

None

{
  "action" : "receive",
  "endpointIdList" : [ "f132bb14-e1d5-4f25-9f7c-a29e4c8effd4" ]
}

None

Status Code	Description
200	The request is processed successfully.
400	Invalid request. Modify the request instead of retrying.
409	The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request.
412	The server does not meet one of the requirements that the requester puts on the request.

Updating a VPC Endpoint Connection

receive: accept the VPC endpoint connection
reject: reject the VPC endpoint connection