vpc:read
Last edited on 28 Aug 2025
Scope Summary
View VPCs
Required Scopes
To add a scope to an API token, you must also add its required scopes. For example, to add a non-read scope for a resource type, you must also add the read scope for that resource type.
The following scopes are required for vpc:read:
| Scope | Description |
|---|---|
regions:read |
View data center regions |
sizes:read |
View Droplet plan sizes |
actions:read |
View events of shared resources that have occurred in the current team |
Associated Scopes
Associated scopes are not required, but they support full functionality of the scope they’re associated with.
For example, to create a Droplet, you need droplet:create. To tag a Droplet during creation, you additionally need tag:create, so tag:create is listed as an associated scope for droplet:create.
The following scopes are associated with vpc:read:
| Scope | Description |
|---|---|
database:read |
View Managed Databases |
load_balancer:read |
View load balancers |
vpc_peering:read |
View VPC Peering |
partner_network_connect:read |
View Partner Network Connect |
droplet:read |
View Droplets |
kubernetes:read |
View Kubernetes clusters but not cluster credentials |