acceptOrRejectVpcPeering

Article summary

Did you find this summary helpful?

Thank you for your feedback

Available in VPC

Specify a VPC peering instance number to accept or reject the VPC peering request.

Request

The following describes the request format for the endpoint. The request format is as follows:

Method	URI
GET, POST	/acceptOrRejectVpcPeering

Request headers

For headers common to all VPC APIs, see VPC common headers.

Request query parameters

The following describes the parameters.

Field	Type	Required	Description
	`regionCode`	String	Optional
`vpcPeeringInstanceNo`	String	Required	Number of the VPC peering instance to accept or reject the VPC peering request Check through getVpcPeeringInstanceList
`isAccept`	Boolean	Required	Whether to accept or reject the VPC peering request `true` \| `false` `true`: request accepted `false`: request rejected
`responseFormatType`	String	Optional	Response result format `xml` (default) \| `json`

Request example

The following is a sample request.

curl --location 'https://ncloud.apigw.ntruss.com/vpc/v2/acceptOrRejectVpcPeering
?regionCode=KR
&vpcPeeringInstanceNo=***6213
&isAccept=true' 
--header 'x-ncp-apigw-timestamp: {Timestamp}'     
--header 'x-ncp-iam-access-key: {Access Key}' 
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'

Response

The following describes the response format.

Response body

See VpcPeeringInstanceList for the response body.

Response status codes

For response status codes common to NAVER Cloud Platform, see Ncloud API response status codes.

Response example

See below for an example.

<acceptOrRejectVpcPeeringResponse>
  <requestId>b4e70022-b05f-4843-9885-7f4444dcc650</requestId>
  <returnCode>0</returnCode>
  <returnMessage>success</returnMessage>
  <totalRows>1</totalRows>
  <vpcPeeringInstanceList>
    <vpcPeeringInstance>
      <vpcPeeringInstanceNo>***6213</vpcPeeringInstanceNo>
      <vpcPeeringName>test-***</vpcPeeringName>
      <regionCode>KR</regionCode>
      <createDate>2020-08-07T18:17:11+0900</createDate>
      <lastModifyDate>2020-08-07T18:17:11+0900</lastModifyDate>
      <vpcPeeringInstanceStatus>
        <code>INIT</code>
        <codeName>init</codeName>
      </vpcPeeringInstanceStatus>
      <vpcPeeringInstanceStatusName>Creating</vpcPeeringInstanceStatusName>
      <vpcPeeringInstanceOperation>
        <code>NULL</code>
        <codeName>NULL OP</codeName>
      </vpcPeeringInstanceOperation>
      <sourceVpcNo>***07</sourceVpcNo>
      <sourceVpcName>test-***</sourceVpcName>
      <sourceVpcIpv4CidrBlock>***.**1.0.0/16</sourceVpcIpv4CidrBlock>
      <sourceVpcLoginId>test-**1@nave.com</sourceVpcLoginId>
      <targetVpcNo>***08</targetVpcNo>
      <targetVpcName>test-***</targetVpcName>
      <targetVpcIpv4CidrBlock>***.**2.0.0/16</targetVpcIpv4CidrBlock>
      <targetVpcLoginId>test-**2@naver.com</targetVpcLoginId>
      <vpcPeeringDescription></vpcPeeringDescription>
      <hasReverseVpcPeering>false</hasReverseVpcPeering>
      <isBetweenAccounts>true</isBetweenAccounts>
      <reverseVpcPeeringInstanceNo></reverseVpcPeeringInstanceNo>
    </vpcPeeringInstance>
  </vpcPeeringInstanceList>
</acceptOrRejectVpcPeeringResponse>

Was this article helpful?

What's Next

createVpcPeeringInstance

Table of contents

Request
Response