Retrieve all VPC Prefixes
Retrieve all VPC Prefixes for the org
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix.
Query parameters
Filter VPC Prefixes by Site, required if the vpcId query parameter is not specified
Filter VPC Prefixes by VPC
Filter VPC Prefixes by Status
Search for matches across all VPC Prefixes. Input will be matched against name and status fields
Related entity to expand
When true, each VPC Prefix object includes usage statistics using the same structure as IP Block usage. Prefix and IP usage data is derived by evaluating associated Ethernet interfaces. Each Interface associated with a VPC Prefix consumes a /31 prefix.
One-indexed page number.
Page number for pagination query
Page size for pagination query
Ordering for pagination query
Response
OK
Example response
[
{
"id": "0c03ba01-d86b-4a57-a41e-cc359b380a6f",
"name": "east-vpc-traffic-net",
"siteId": "ea144def-d68f-44c3-9485-4b103fa2686f",
"vpcId": "5e28ad7c-5fb7-46d6-a28a-fc0ba6fdc4a3",
"prefix": "192.168.1.0/24",
"ipBlockId": "8c1d1a06-90a2-4863-8ee1-6029265b9f0a",
"prefixLength": 24,
"status": "Ready",
"usageStats": {
"availableIPs": 256,
"acquiredIPs": 2,
"availablePrefixes": [
"192.168.1.0/28",
"192.168.1.16/30",
"192.168.1.24/29",
"192.168.1.32/27",
"192.168.1.64/26",
"192.168.1.128/25"
],
"availableSmallestPrefixes": 63,
"acquiredPrefixes": 1
},
"statusHistory": [
{
"status": "Ready",
"message": "Received VPC prefix creation request, ready",
"created": "2019-08-24T14:15:22Z",
"updated": "2019-08-24T14:15:22Z"
}
],
"created": "2019-08-24T14:15:22Z",
"updated": "2019-08-24T14:15:22Z"
}
]