Skip to content
StratumStratum Docs

List the static routes on a route table.

GET
/v1/projects/{projectId}/network/route-tables/{routeTableId}/routes
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/projects/example/network/route-tables/example/routes \
  --header 'Authorization: Bearer <token>'

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
projectId
required
string
/^p-[a-z0-9-]+$/
routeTableId
required
string
/^rtb-[a-z0-9-]+$/

Responses

Section titled “Responses”

200

Section titled “200”

Routes.

Media typeapplication/json
object
items
required
Array<object>
object
destinationCidr
required

IPv4 CIDR this route matches on the destination address. Must not lie inside the VPC CIDR (intra-VPC routing is implicit) or link-local space; broad routes containing them (e.g. 0.0.0.0/0) are fine — local traffic always wins, as with AWS’s non-overridable local route.

string
/^([0-9]{1,3}\.){3}[0-9]{1,3}/[0-9]+$/
targetType
required
string
Allowed values: internetGateway networkInterface instance natGateway vpcPeering
targetId

Target resource ID. Required for every target type except internetGateway (a VPC has at most one implicit IGW). For instance targets this is the instance ID; the route resolves to its primary NIC.

string
state

Server-populated; ignored on input. A route whose target no longer exists is reported as blackhole and not programmed into the fabric.

string
Allowed values: active blackhole

Example 

{
  "items": [
    {
      "targetType": "internetGateway",
      "state": "active"
    }
  ]
}

404

Section titled “404”

Resource not found.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example 

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}