Digital Ocean Reserved IPs API
As of 16 June 2022, we have renamed the [Floating IP](https://docs.digitalocean.com/reference/api/api-reference/#tag/Floating-IPs)product to Reserved IPs. The Reserved IP product's endpoints function the exactsame way as Floating IPs. The only difference is the name change throughout theURLs and fields. For example, the `floating_ips` field is now the `reserved_ips` field.The Floating IP endpoints will remain active until fall 2023 before beingpermanently deprecated.With the exception of the [Projects API](https://docs.digitalocean.com/reference/api/api-reference/#tag/Projects),we will reflect this change as an additional field in the responses across the APIwhere the `floating_ip` field is used. For example, the Droplet metadata responsewill contain the field `reserved_ips` in addition to the `floating_ips` field.Floating IPs retrieved using the Projects API will retain the original name.DigitalOcean Reserved IPs are publicly-accessible static IP addresses that can bemapped to one of your Droplets. They can be used to create highly availablesetups or other configurations requiring movable addresses.Reserved IPs are bound to a specific region.
Digital Ocean Reserved IPs API is one of 37 APIs that Digital Ocean publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Reserved IPs. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 4 operations across 2 paths, and defines 30 schemas. It is described by OpenAPI 3.0.0, at version 2.0.
Requests are made against a single base URL, https://api.digitalocean.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Digital Ocean Reserved IPs API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearer_auth).
By default, every request must be authenticated.
bearer_auth— OAuth Authentication In order to interact with the DigitalOcean API, you or your application must authenticate. The DigitalOcean API handles this through OAuth…
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
As of 16 June 2022, we have renamed the [Floating IP](https://docs.digitalocean.com/reference/api/api-reference/tag/Floating-IPs) product to Reserved IPs. The Reserved IP product'…
Schemas 30
The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are droplet (23 properties), image (14 properties), size (12 properties), reserved_ip (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Digital Ocean 12
Other APIs Digital Ocean publishes across the network.
This is an independent, third-party profile of Digital Ocean Reserved IPs 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.