List route tables in a project.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/network/route-tables \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Route tables.
object
object
True for the VPC’s main route table (auto-created with the VPC; subnets not explicitly associated with a custom table use it). The main table cannot be deleted.
object
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.
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.
Server-populated; ignored on input. A route whose target no longer exists is reported as blackhole and not programmed into the fabric.
Subnets currently associated with this table.
AWS-shape resource tags. Freeform UTF-8 keys (1-128 bytes, no
leading/trailing whitespace) mapped to freeform UTF-8 values
(0-256 bytes). Max 50 tags per resource. Reserved prefixes
(stratum.dev/, stratum.platform_health., stratum:,
aws:) return 400 RESERVED_NAMESPACE on customer input.
PATCH replaces the whole map..
object
True when the server had more rows than it returned. The response is a valid prefix of the result, not the whole of it.
Without this flag a client at the server’s row ceiling receives a full
page and no nextPageToken, which means “this is
the complete set” — so data it never saw would be indistinguishable
from data that does not exist.
It does not imply a cursor exists. These queries do not all sort on a total order, so a resumable token cannot be minted for them yet. The remedy is to narrow the request (a filter, or a tighter scope), not to page.
Example
{ "items": [ { "routes": [ { "targetType": "internetGateway", "state": "active" } ], "state": "available" } ]}