Complete reference documentation for the DigitalOcean API, including request samples in cURL, Python, Go, and Ruby.
API Overview
Validated on 23 Jan 2025 • Last edited on 17 Apr 2025
DigitalOcean has four APIs that let you programmatically manage and interact with various products and parts of the platform.
DigitalOcean API
The DigitalOcean API lets you programmatically manage Droplets and other DigitalOcean resources using conventional HTTP requests.
Create a personal access token for use with the DigitalOcean API.
Spaces API
Spaces provides a RESTful XML API for programmatically managing the data you store through standard HTTP requests. The API is interoperable with Amazon’s AWS S3 API, allowing you to interact with the service with any S3-compatible tools.
Complete reference documentation for the Spaces RESTful XML API, which is interoperable with Amazon’s AWS S3 API.
Allow people or programs to co-manage Spaces with the owner of the Spaces bucket using access keys or DigitalOcean Teams.
The Spaces API is inter-operable with the AWS S3 API, meaning you can use existing S3 tools and libraries with it. These examples demonstrate how to perform a number of common Spaces operations in JavaScript, Go, PHP, Python 3, and Ruby.
OAuth API
The OAuth API is a secure method for authenticating users and allowing third-party applications limited access to your servers or DigitalOcean user accounts.
Complete reference documentation for the OAuth API, including application registration and troubleshooting.
Metadata API
The metadata API allows a Droplet to access information about itself including user data, Droplet ID, datacenter region, and IP addresses. Droplets can access the metadata service using the static, link-local IP address 169.254.169.254
.
Complete reference documentation for the Metadata API for Droplets.
Use the Droplet metadata service to programmatically query a Droplet for information about itself.
Latest Updates
3 April 2025
-
We previously announced an upcoming breaking change to the DigitalOcean API to fix an incomplete resource authorization issue. We have changed our approach so that this is no longer a breaking change.
Originally, some users would need to recreate API tokens with additional scopes to retain the same functionality. Now, API tokens created before we deploy the fix retain the same functionality and access to the API. No action is required to continue using these tokens as before.
Learn more on Breaking Change to Fix DigitalOcean API Incomplete Resource Authorization Issue.
28 February 2025
-
All managed databases except MongoDB now support up to 2,000 IP addresses as trusted sources. To add trusted sources, see our guides for MySQL, PostgreSQL, Caching, MongoDB, OpenSearch, and Kafka.
20 February 2025
-
In April 2025, we are implementing a breaking change to the DigitalOcean API that fixes an incomplete resource authorization issue. You may need to recreate API tokens with additional scopes to retain the same functionality, depending on your use cases.
For more information, see the full release notes.