How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vultr private Networks API

[Private Networks](https://www.vultr.com/docs/configuring-private-network) are fully isolated networks accessible only by instances on your account. Each private network is only available in one Region and cannot span across regions. An [instance](#tag/instances) can connect to [multiple private networks](https://www.vultr.com/docs/multiple-private-networks) and you may have up to 5 private networks per [region](#tag/region).

Vultr private Networks API is one of 46 APIs that Vultr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 12 JSON Schema definitions.

Tagged areas include Private Networks. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 5 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.vultr.com/v2.

5 operations 2 paths 13 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.vultr.com/v2
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Vultr private Networks API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (API_Key). It accepts HTTP bearer tokens (API Key). By default, every request must be authenticated.

  • API_Key — The Vultr API v2 uses API keys for authentication. You can manage your API keys in the Vultr customer portal. Please do not share API keys publicly, or embed t…
  • API Key — The Vultr API v2 uses API keys for authentication. You can manage your API keys in the Vultr customer portal. Please do not share API keys publicly, or embed t…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

private Networks 5

Private Networks are fully isolated networks accessible only by instances on your account. Each private network is only available in one Region and cannot span across regions. An…

GET
/private-networks/{network-id}
Get a private network
get-network 1 param → 200400401403404
DELETE
/private-networks/{network-id}
Delete a private network
delete-network 1 param → 204400401403404
PUT
/private-networks/{network-id}
Update a Private Network
update-network 1 param body → 204400401403404
GET
/private-networks
List Private Networks
list-networks 2 params → 200400401403404
POST
/private-networks
Create a Private Network
create-network body → 201400401404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are network (6 properties), network_2 (6 properties), network_3 (6 properties), create_network_request (4 properties). Each schema is shown below with its type and property counts.

network
object
Network information.
6 properties 1 required
meta
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
meta_2
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
list_networks_200_response
object
2 properties
update_network_request
object
1 property 1 required
get_network_200_response
object
1 property
meta_links
object
Cursor values for pagination.
2 properties
network_2
object
Network information.
6 properties 1 required
create_network_request
object
4 properties 1 required
meta_3
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
list_networks_200_response_2
object
2 properties
get_network_200_response_2
object
1 property
network_3
object
Network information.
6 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vultr-private-networks-api-openapi.yml Raw ↑

Other APIs Vultr publishes across the network.

Vultr Account API
Vultr Application API
Vultr Backup API
Vultr Baremetal API
Vultr Billing API
Vultr Block API
Vultr Container Registry API
Vultr Dns API
Vultr Firewall API
Vultr IAM Assumed Roles API
Vultr IAM Endpoint Actions API
Vultr IAM Groups API
Where this information came from

This is an independent, third-party profile of Vultr private Networks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.