removeRoute

Article summary

Did you find this summary helpful?

Thank you for your feedback

Available in VPC

Remove the route list set in a route table. Default routes can't be removed.

Request

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

Method	URI
GET, POST	/removeRoute

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	Region code of the route table whose route you want to remove First Region of the search result (default) Check through getRegionList
`vpcNo`	String	Required	VPC number of the route table Check through getVpcList
`routeList.N.destinationCidrBlock`	String	Required	Range of destination IPv4 addresses for the route you want to remove Use CIDR notation <E.g.> routeList.1.destinationCidrBlock=0.0.0.0/0&routeList.2.destinationCidrBlock=100.10.20.0/24
`routeList.N.targetTypeCode`	String	Required	Destination type of the route to remove `NATGW` \| `VPCPEERING` \| `VGW` `NATGW`: NAT Gateway `VPCPEERING`: VPC Peering `VGW`: Virtual Private Gateway <E.g.> routeList.1.targetTypeCode=NATGW&routeList.2.targetTypeCode=VPCPEERING
`routeList.N.targetNo`	String	Required	Destination identification number of the route to delete Check via API to view the list of resources for each destination type <E.g.> routeList.1.targetNo=1234&routeList.2.targetNo=2345
`routeList.N.targetName`	String	Required	Destination name of the route to delete Check via API to view the list of resources for each destination type <E.g.> routeList.1.targetName=test-natgateway&routeList.2.targetName=test-peering
	`responseFormatType`	String	Optional

Request example

The following is a sample request.

curl --location 'https://ncloud.apigw.ntruss.com/vpc/v2/removeRoute
?regionCode=KR
&vpcNo=***04
&routeTableNo=***38
&routeList.1.destinationCidrBlock=***.***.200.0/24
&routeList.1.targetTypeCode=NATGW
&routeList.1.targetNo=***9734
&routeList.1.targetName=test-***'
--header 'x-ncp-iam-access-key: {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 RouteList for the response body.

Response status codes

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

Response example

The following is a sample response.

<removeRouteResponse>
  <requestId>fb1ea6cf-15bf-4600-b737-1d7bed33421e</requestId>
  <returnCode>0</returnCode>
  <returnMessage>success</returnMessage>
  <totalRows>2</totalRows>
  <routeList>
    <route>
      <destinationCidrBlock>***.***.0.0/16</destinationCidrBlock>
      <targetName>LOCAL</targetName>
      <routeTableNo>***38</routeTableNo>
      <targetType>
        <code>LOCAL</code>
        <codeName>Local</codeName>
      </targetType>
      <targetNo></targetNo>
      <isDefault>true</isDefault>
    </route>
    <route>
      <destinationCidrBlock>***.***.0.0/0</destinationCidrBlock>
      <targetName>INTERNET GATEWAY</targetName>
      <routeTableNo>***38</routeTableNo>
      <targetType>
        <code>IGW</code>
        <codeName>Internet Gateway</codeName>
      </targetType>
      <targetNo></targetNo>
      <isDefault>true</isDefault>
    </route>
  </routeList>
</removeRouteResponse>

Was this article helpful?

What's Next

addRouteTableSubnet

Table of contents

Request
Response