VPC API Reference
Last verified 4 Nov 2026
A Virtual Private Cloud (VPC) is a private network interface for collections of DigitalOcean resources. VPC networks are inaccessible from the public internet and other VPC networks, and traffic on them doesn’t count against bandwidth usage. You can link VPC networks to each other using VPC peering connections.
The VPC API endpoints are organized into the following groups:
- VPCs (10 endpoints): VPCs (virtual private clouds) allow you to create virtual networks containing resources that can communicate with each other in full isolation using private IP addresses.
- VPC Peerings (5 endpoints): VPC Peerings join two VPC networks with a secure, private connection. This allows resources in those networks to connect to each other’s private IP addresses as if they were in the same network.
- VPC NAT Gateways (5 endpoints): VPC NAT Gateways allow resources in a private VPC to access the public internet without exposing them to incoming traffic.
- VPC Routes [Public Preview] (5 endpoints): Routes control how traffic from resources in VPC subnets reaches destination networks. VPC-scoped routes are read-only, while customer-managed static routes can be added to individual VPC subnets.
- VPC Subnets [Public Preview] (6 endpoints): VPC subnets divide a VPC network into isolated IP ranges. You can create, retrieve, rename, list, and delete subnets within a VPC.