List Client VPN endpoints in a project.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/network/client-vpn-endpoints \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Return endpoints attached to this VPC.
Responses
Section titled “Responses”Client VPN endpoints.
object
A per-VPC WireGuard terminator for remote user access
(AWS-Client-VPN-shaped). serverPublicKey is populated once the
data-plane terminator is provisioned.
object
The address pool handed to connecting clients (IPv4 /16../22).
True routes only VPC/authorized CIDRs; false is a full tunnel.
Pushed resolvers; empty means the VPC.3 resolver default.
Emit per-connection events to observability.
WireGuard server public key; empty until the terminator is provisioned.
The floating IP DNAT’d to the terminator for public ingress; empty when none is bound.
The terminator’s reachable “
Tenant subnets the endpoint has an interface in.
Security groups governing who may reach the endpoint. Empty when the endpoint uses the pre- shared-transit path, where ingress is all-or-nothing on the floating IP association.
The Stratum-owned NICs backing this endpoint, one per subnet. These carry the security groups and their addresses are what the floating IP forwards to. Empty means the endpoint is on the shared-transit path and its security groups, if any, govern nothing.
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": [ { "authMode": "oidc", "state": "creating" } ]}