---
title: "getRouteTableDetail"
slug: "networking-vpc-routetable-getroutetabledetail"
updated: 2026-09-17T10:12:33Z
published: 2026-09-17T10:12:33Z
canonical: "api.ncloud-docs.com/networking-vpc-routetable-getroutetabledetail"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# getRouteTableDetail

Available in VPC

Get the details of a route table by specifying the route table number.

## Request

This section describes the request format. The method and URI are as follows:

| Method | URI |
| --- | --- |
| GET \| POST | /vpc/v2/getRouteTableDetail |

Note

This guide is based on the GET method. POST method call tests can be performed through Swagger in the API Gateway service of the NAVER Cloud Platform console.

### Request headers

For information about the headers common to all VPC APIs, see [VPC common headers](/docs/en/networking-vpc#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94).

### Request query parameters

You can use the following query parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `regionCode` | String | Optional | Region code where you want to query the route table information - First Region of the query result (default) - See [getRegionList](/docs/en/compute-vserver-server-common-getregionlist). |
| `routeTableNo` | String | Required | Number of the route table to query - See [getRouteTableList](/docs/en/networking-vpc-routetable-getroutetablelist). |
| `responseFormatType` | String | Optional | Format of the response result - `xml` (default) \| `json` |

### Request example

The request example is as follows:

```
curl --location 'https://ncloud.apigw.ntruss.com/vpc/v2/getRouteTableDetail
?regionCode=KR
&routeTableNo=***38' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'
```

## Response

This section describes the response format.

### Response body

See [RouteTableList](/docs/en/common-vapidatatype-routetablelist) for the response body.

### Response status codes

For information about the HTTP status codes common to all VPC APIs, see [VPC response status codes](/docs/en/networking-vpc#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C).

### Response example

The response example is as follows:

```
<getRouteTableDetailResponse>
  <requestId>3fc9c7c0-7319-48d4-bea4-f14f594417ed</requestId>
  <returnCode>0</returnCode>
  <returnMessage>success</returnMessage>
  <totalRows>1</totalRows>
  <routeTableList>
    <routeTable>
      <routeTableNo>***38</routeTableNo>
      <routeTableName>test-***</routeTableName>
      <regionCode>KR</regionCode>
      <vpcNo>***04</vpcNo>
      <supportedSubnetType>
        <code>PUBLIC</code>
        <codeName>Public</codeName>
      </supportedSubnetType>
      <isDefault>false</isDefault>
      <routeTableStatus>
        <code>RUN</code>
        <codeName>run</codeName>
      </routeTableStatus>
      <routeTableDescription></routeTableDescription>
    </routeTable>
  </routeTableList>
</getRouteTableDetailResponse>
```