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 Reserved Ip API

IP addresses can be [reserved](https://my.vultr.com/network/) and moved between [instances](#tag/instances). Reserved IPs can also be used as [floating addresses](https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-bgp) for high-availability.

Vultr Reserved Ip 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 reserved-ip. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 8 operations across 5 paths, and defines 15 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.

8 operations 5 paths 15 schemas 1 DELETE2 GET1 PATCH4 POST

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 Reserved Ip 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 8

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

reserved-ip 8

IP addresses can be reserved and moved between instances. Reserved IPs can also be used as floating addresses for high-availability.

GET
/reserved-ips/{reserved-ip}
Get Reserved IP
get-reserved-ip 1 param → 200400401404
DELETE
/reserved-ips/{reserved-ip}
Delete Reserved IP
delete-reserved-ip 1 param → 204400401
PATCH
/reserved-ips/{reserved-ip}
Update Reserved IP
patch-reserved-ips-reserved-ip 2 params body → 200400401404
GET
/reserved-ips
List Reserved IPs
list-reserved-ips 2 params → 200400401404
POST
/reserved-ips
Create Reserved IP
create-reserved-ip body → 201400401404
POST
/reserved-ips/{reserved-ip}/attach
Attach Reserved IP
attach-reserved-ip 1 param body → 204400401404
POST
/reserved-ips/{reserved-ip}/detach
Detach Reserved IP
detach-reserved-ip 1 param → 204400401404
POST
/reserved-ips/convert
Convert Instance IP to Reserved IP
convert-reserved-ip body → 201400401404

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are reserved-ip (7 properties), reserved-ip_2 (7 properties), reserved-ip_3 (7 properties), create_reserved_ip_request (3 properties). Each schema is shown below with its type and property counts.

reserved-ip
object
Reserved IP information.
7 properties
meta
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
list_reserved_ips_200_response
object
2 properties
meta_2
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
patch_reserved_ips_reserved_ip_request
object
1 property 1 required
convert_reserved_ip_request
object
2 properties 1 required
create_reserved_ip_request
object
3 properties 2 required
attach_reserved_ip_request
object
1 property 1 required
reserved-ip_2
object
Reserved IP information.
7 properties
meta_links
object
Cursor values for pagination.
2 properties
get_reserved_ip_200_response
object
1 property
list_reserved_ips_200_response_2
object
2 properties
meta_3
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
reserved-ip_3
object
Reserved IP information.
7 properties
get_reserved_ip_200_response_2
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vultr-reserved-ip-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 Reserved Ip 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.