Help Center/ Enterprise Router/ API Reference/ APIs/ Routes/ Querying Effective Routes

Updated on 2025-03-31 GMT+08:00

View PDF

Querying Effective Routes

Function

This API is used to query effective routes. Pagination query is supported. Effective routes are preferred routes.

Calling Method

For details, see Calling APIs.

URI

GET /v3/{project_id}/enterprise-router/route-tables/{route_table_id}/routes

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID
route_table_id	Yes	String	Route table ID

**Table 2** Query Parameters
Parameter	Mandatory	Type	Description
limit	No	Integer	Number of records on each page. Value range: 0 to 2000 Minimum: 0 Maximum: 2000
marker	No	String	ID of the last route on the previous page. If this parameter is left blank, the first page is queried. This parameter must be used together with limit. Minimum: 1 Maximum: 128
destination	No	Array of strings	Destination address of a route
resource_type	No	Array of strings	vpc: VPC vpn: VPN gateway vgw: Direct Connect virtual gateway peering: peering connection. A cloud connection is used to connect two enterprise routers from different regions. gdgw: global DC gateway

Request Parameters

None

Response Parameters

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
routes	Array of EffectiveRoute objects	Routes
request_id	String	Request ID
page_info	PageInfo object	Pagination query information

**Table 4** EffectiveRoute
Parameter	Type	Description
route_id	String	Route ID
destination	String	Destination address of a route
next_hops	Array of EffectiveRouteAttachment objects	Next hops of the routes
is_blackhole	Boolean	Whether the route is a blackhole route
route_type	String	Route type. Value options: static and propagation
description	String	Route description

**Table 5** EffectiveRouteAttachment
Parameter	Type	Description
resource_id	String	Attached resource ID on its own service console
resource_type	String	Attachment type. vpc: VPC vpn: VPN gateway vgw: Direct Connect virtual gateway peering: peering connection. A cloud connection is used to connect two enterprise routers from different regions. gdgw: global DC gateway
attachment_id	String	Attachment ID

**Table 6** PageInfo
Parameter	Type	Description
next_marker	String	Marker of the next page. The value is the resource UUID. If the value is empty, the resource is on the last page.
current_count	Integer	Number of resources in the list

Example Requests

Querying effective routes

GET https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/route-tables/915a14a6-867b-4af7-83d1-70efceb146f9/routes

Example Responses

Status code: 200

{
  "routes" : [ {
    "route_id" : "9b3b38a9-1c9d-4f01-9429-81af6b545289",
    "destination" : "192.168.0.0/16",
    "description" : "static route",
    "next_hops" : [ {
      "resource_id" : "9c4ab06a-0ab4-4fad-93a8-f733f3a4433d",
      "resource_type" : "vpc",
      "attachment_id" : "9b3b38a9-1c9d-4f01-9429-81af6b545289"
    } ],
    "is_blackhole" : false,
    "route_type" : "static"
  } ],
  "page_info" : {
    "next_marker" : "1",
    "current_count" : 1
  },
  "request_id" : "915a14a6-867b-4af7-83d1-70efceb146f9"
}