[metadata]
color-scheme: light dark
description: The DigitalOcean API allows you to manage Droplets and resources within the DigitalOcean cloud in a simple, programmatic way using conventional HTTP …
generator: Hugo 0.161.1
google-site-verification: CAYPZwe7daX8KlYYZfB4VMjfT4g8Tqrrc4Q3g_wMvI8
keywords: DigitalOcean, cloud computing
og:site_name: DigitalOcean
og:type: article
twitter:card: summary_large_image
twitter:creator: @DigitalOcean
twitter:site: DigitalOcean
twitter:url: https://docs.digitalocean.com/reference/api/reference/public-apis/
viewport: width=device-width, initial-scale=1

[canonical-links]
https://docs.digitalocean.com/reference/api/reference/public-apis/

[document-links]
1-Click Applications 2 endpoints: /reference/api/reference/1-click-applications/
1-Click Applications: /reference/api/reference/1-click-applications/
API Reference: https://docs.digitalocean.com/reference/api
APIs: /reference/api/
About: https://www.digitalocean.com/about
Access Metadata: /products/droplets/how-to/access-metadata/
Account 1 endpoint: /reference/api/reference/account/
Account: /reference/api/reference/account/
Actions 2 endpoints: /reference/api/reference/actions/
Actions: /reference/api/reference/actions/
Add-Ons 8 endpoints: /reference/api/reference/add-ons/
Add-Ons: /reference/api/reference/add-ons/
Ansible: /reference/ansible/
Apps & API: https://cloud.digitalocean.com/settings/applications
Apps 38 endpoints: /reference/api/reference/apps/
Apps: /reference/api/reference/apps/
BYOIP Prefixes 6 endpoints: /reference/api/reference/byoip-prefixes/
BYOIP Prefixes: /reference/api/reference/byoip-prefixes/
Billing 8 endpoints: /reference/api/reference/billing/
Billing: /reference/api/reference/billing/
Block Storage 9 endpoints: /reference/api/reference/block-storage/
Block Storage Actions 4 endpoints: /reference/api/reference/block-storage-actions/
Block Storage Actions: /reference/api/reference/block-storage-actions/
Block Storage: /reference/api/reference/block-storage/
Blog: https://www.digitalocean.com/blog
CDN Endpoints 6 endpoints: /reference/api/reference/cdn-endpoints/
CDN Endpoints: /reference/api/reference/cdn-endpoints/
CLI Reference: https://docs.digitalocean.com/reference/doctl
Careers: https://www.digitalocean.com/careers
Certificates 4 endpoints: /reference/api/reference/certificates/
Certificates: /reference/api/reference/certificates/
Code of Conduct: https://www.digitalocean.com/community/pages/code-of-conduct
Container Registries 19 endpoints: /reference/api/reference/container-registries/
Container Registries: /reference/api/reference/container-registries/
Container Registry 18 endpoints: /reference/api/reference/container-registry/
Container Registry: /reference/api/reference/container-registry/
Create an Access Token: /reference/api/create-personal-access-token/
Currents Research: https://www.digitalocean.com/currents
Databases 71 endpoints: /reference/api/reference/databases/
Databases: /reference/api/reference/databases/
Dedicated Inference 13 endpoints: /reference/api/reference/dedicated-inference/
Dedicated Inference: /reference/api/reference/dedicated-inference/
DigitalOcean API: /reference/api/#digitalocean
Docs Home: https://docs.digitalocean.com
Docs: https://docs.digitalocean.com/
Domain Records 6 endpoints: /reference/api/reference/domain-records/
Domain Records: /reference/api/reference/domain-records/
Domains 4 endpoints: /reference/api/reference/domains/
Domains: /reference/api/reference/domains/
Droplet Actions 4 endpoints: /reference/api/reference/droplet-actions/
Droplet Actions: /reference/api/reference/droplet-actions/
Droplet Autoscale Pools 8 endpoints: /reference/api/reference/droplet-autoscale-pools/
Droplet Autoscale Pools: /reference/api/reference/droplet-autoscale-pools/
Droplets 19 endpoints: /reference/api/reference/droplets/
Droplets: /reference/api/reference/droplets/
Firewalls 11 endpoints: /reference/api/reference/firewalls/
Firewalls: /reference/api/reference/firewalls/
Floating IP Actions 3 endpoints: /reference/api/reference/floating-ip-actions/
Floating IP Actions: /reference/api/reference/floating-ip-actions/
Floating IPs 4 endpoints: /reference/api/reference/floating-ips/
Floating IPs: /reference/api/reference/floating-ips/
Functions 13 endpoints: /reference/api/reference/functions/
Functions: /reference/api/reference/functions/
Give Feedback: https://ideas.digitalocean.com/documentation
GradientAI Platform 119 endpoints: /reference/api/reference/gradientai-platform/
GradientAI Platform: /reference/api/reference/gradientai-platform/
Image Actions 3 endpoints: /reference/api/reference/image-actions/
Image Actions: /reference/api/reference/image-actions/
Images 9 endpoints: /reference/api/reference/images/
Images: /reference/api/reference/images/
Inference APIs: /reference/api/reference/inference-apis/
Kubernetes 28 endpoints: /reference/api/reference/kubernetes/
Kubernetes: /reference/api/reference/kubernetes/
Legal: https://www.digitalocean.com/legal
Libraries: /reference/libraries/
Load Balancers 10 endpoints: /reference/api/reference/load-balancers/
Load Balancers: /reference/api/reference/load-balancers/
MCP Server: /reference/mcp/
Manage Model Access Keys: /products/inference/how-to/manage-model-access-keys/
Metadata API: /reference/api/#metadata
Monitoring 72 endpoints: /reference/api/reference/monitoring/
Monitoring: /reference/api/reference/monitoring/
NFS 11 endpoints: /reference/api/reference/nfs/
NFS Actions 1 endpoint: /reference/api/reference/nfs-actions/
NFS Actions: /reference/api/reference/nfs-actions/
NFS: /reference/api/reference/nfs/
OAuth API: /reference/api/oauth/
Open Source: /reference/opensource/
Organizations 2 endpoints: /reference/api/reference/organizations/
Organizations: /reference/api/reference/organizations/
Paperspace: /reference/paperspace/
Partner Network Connect 9 endpoints: /reference/api/reference/partner-network-connect/
Partner Network Connect: /reference/api/reference/partner-network-connect/
Platform: https://docs.digitalocean.com/platform/
Products: https://docs.digitalocean.com/products/
Project Resources 4 endpoints: /reference/api/reference/project-resources/
Project Resources: /reference/api/reference/project-resources/
Projects 9 endpoints: /reference/api/reference/projects/
Projects: /reference/api/reference/projects/
Public APIs: /reference/api/reference/public-apis/
PyDo: /reference/pydo/
Q&A: https://www.digitalocean.com/community/questions
Reference: /reference/api/digitalocean/
Reference: /reference/api/metadata/
Reference: /reference/api/reference/
Reference: /reference/api/spaces/
Reference: https://docs.digitalocean.com/reference/
Regions 1 endpoint: /reference/api/reference/regions/
Regions: /reference/api/reference/regions/
Release Notes: https://docs.digitalocean.com/release-notes
Report Abuse: https://www.digitalocean.com/company/contact/abuse
Reserved IP Actions 3 endpoints: /reference/api/reference/reserved-ip-actions/
Reserved IP Actions: /reference/api/reference/reserved-ip-actions/
Reserved IPs 4 endpoints: /reference/api/reference/reserved-ips/
Reserved IPs: /reference/api/reference/reserved-ips/
Reserved IPv6 4 endpoints: /reference/api/reference/reserved-ipv6/
Reserved IPv6 Actions 1 endpoint: /reference/api/reference/reserved-ipv6-actions/
Reserved IPv6 Actions: /reference/api/reference/reserved-ipv6-actions/
Reserved IPv6: /reference/api/reference/reserved-ipv6/
SSH Keys 5 endpoints: /reference/api/reference/ssh-keys/
SSH Keys: /reference/api/reference/ssh-keys/
Security 10 endpoints: /reference/api/reference/security/
Security: /reference/api/reference/security/
Sign Up: https://cloud.digitalocean.com/registrations/new
Sizes 1 endpoint: /reference/api/reference/sizes/
Sizes: /reference/api/reference/sizes/
Snapshots 3 endpoints: /reference/api/reference/snapshots/
Snapshots: /reference/api/reference/snapshots/
Spaces API: /reference/api/#spaces
Spaces Keys 6 endpoints: /reference/api/reference/spaces-keys/
Spaces Keys: /reference/api/reference/spaces-keys/
Support Center: /support
Support: https://docs.digitalocean.com/support/
Tags 6 endpoints: /reference/api/reference/tags/
Tags: /reference/api/reference/tags/
Terraform: /reference/terraform/
Token Scopes: /reference/api/scopes/
Trust Platform: https://www.digitalocean.com/trust
Tutorials: https://www.digitalocean.com/community/tutorials
Unix epoch time: http://en.wikipedia.org/wiki/Unix_time
Uptime 11 endpoints: /reference/api/reference/uptime/
Uptime: /reference/api/reference/uptime/
VPC NAT Gateways 5 endpoints: /reference/api/reference/vpc-nat-gateways/
VPC NAT Gateways: /reference/api/reference/vpc-nat-gateways/
VPC Peerings 5 endpoints: /reference/api/reference/vpc-peerings/
VPC Peerings: /reference/api/reference/vpc-peerings/
VPCs 10 endpoints: /reference/api/reference/vpcs/
VPCs: /reference/api/reference/vpcs/
Vector Databases 11 endpoints: /reference/api/reference/vector-databases/
Vector Databases: /reference/api/reference/vector-databases/
View page as Markdown: /reference/api/reference/public-apis/index.html.md
Write for DOnations: https://www.digitalocean.com/community/pages/write-for-digitalocean
community tutorial: https://www.digitalocean.com/community/tutorials/how-to-install-the-windows-subsystem-for-linux-2-on-microsoft-windows-10
doctl CLI: /reference/doctl/
https://discord.gg/digitalocean
https://docs.digitalocean.com/llms.txt: https://docs.digitalocean.com/llms.txt
https://github.com/digitalocean
https://www.facebook.com/DigitalOceanCloudHosting
https://www.instagram.com/thedigitalocean
https://www.linkedin.com/company/digitalocean
https://www.youtube.com/DigitalOcean
https://x.com/digitalocean
llms.txt: https://docs.digitalocean.com/llms.txt
payload: https://docs.digitalocean.com/reference/api/api-reference/#cdn_purge_cache
syntax: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.2
syntax: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/set_1

[content]
Public APIs | DigitalOcean Documentation
Docs
Platform
Products
Reference
Support
Sign Up
doctl CLI
APIs
DigitalOcean API
Reference
Inference APIs
Public APIs
1-Click Applications
Account
Actions
Add-Ons
Apps
Billing
Block Storage
Block Storage Actions
BYOIP Prefixes
CDN Endpoints
Certificates
Container Registries
Container Registry
Databases
Dedicated Inference
Domain Records
Domains
Droplet Actions
Droplet Autoscale Pools
Droplets
Firewalls
Floating IP Actions
Floating IPs
Functions
GradientAI Platform
Image Actions
Images
Kubernetes
Load Balancers
Monitoring
NFS
NFS Actions
Organizations
Partner Network Connect
Project Resources
Projects
Regions
Reserved IP Actions
Reserved IPs
Reserved IPv6
Reserved IPv6 Actions
Security
Sizes
Snapshots
Spaces Keys
SSH Keys
Tags
Uptime
Vector Databases
VPC NAT Gateways
VPC Peerings
VPCs
Create an Access Token
Manage Model Access Keys
Spaces API
Reference
OAuth API
Metadata API
Reference
Access Metadata
Token Scopes
Reference
MCP Server
Paperspace
Ansible
Terraform
PyDo
Libraries
Open Source
DigitalOcean API
Reference
Public APIs
Give Feedback
For AI agents:
The documentation index is at
https://docs.digitalocean.com/llms.txt
. Markdown versions of pages use the same URL with
index.html.md
in place of the HTML page (for example, append
index.html.md
to the directory path instead of opening the HTML document).
Public APIs
Generated on 1 Jan 0001
Copy page as Markdown
View page as Markdown
The DigitalOcean API allows you to manage Droplets and resources within the DigitalOcean cloud in a simple, programmatic way using conventional HTTP requests.
All of the functionality that you are familiar with in the DigitalOcean control panel is also available through the API, allowing you to script the complex actions that your situation requires.
The API documentation will start with a general overview about the design and technology that has been implemented, followed by reference information about specific endpoints.
Requests
Any tool that is fluent in HTTP can communicate with the API simply by requesting the correct URI. Requests should be made using the HTTPS protocol so that traffic is encrypted. The interface responds to different methods depending on the action required.
Method
Usage
GET
For simple retrieval of information about your account, Droplets, or environment, you should use the GET method. The information you request will be returned to you as a JSON object. The attributes defined by the JSON object can be used to form additional requests. Any request using the GET method is read-only and will not affect any of the objects you are querying.
DELETE
To destroy a resource and remove it from your account and environment, the DELETE method should be used. This will remove the specified object if it is found. If it is not found, the operation will return a response indicating that the object was not found. This idempotency means that you do not have to check for a resource’s availability prior to issuing a delete command, the final state will be the same regardless of its existence.
PUT
To update the information about a resource in your account, the PUT method is available. Like the DELETE Method, the PUT method is idempotent. It sets the state of the target using the provided values, regardless of their current values. Requests using the PUT method do not need to check the current attributes of the object.
PATCH
Some resources support partial modification. In these cases, the PATCH method is available. Unlike PUT which generally requires a complete representation of a resource, a PATCH request is a set of instructions on how to modify a resource updating only specific attributes.
POST
To create a new object, your request should specify the POST method. The POST request includes all of the attributes necessary to create a new object. When you wish to create a new object, send a POST request to the target endpoint.
HEAD
Finally, to retrieve metadata information, you should use the HEAD method to get the headers. This returns only the header of what would be returned with an associated GET request. Response headers contain some useful information about your API access and the results that are available for your request. For instance, the headers contain your current rate-limit value and the amount of time available until the limit resets. It also contains metrics about the total number of objects found, pagination information, and the total content length.
HTTP Statuses
Along with the HTTP methods that the API responds to, it will also return standard HTTP statuses, including error codes.
In the event of a problem, the status will contain the error code, while the body of the response will usually contain additional information about the problem that was encountered.
In general, if the status returned is in the 200 range, it indicates that the request was fulfilled successfully and that no error was encountered.
Return codes in the 400 range typically indicate that there was an issue with the request that was sent. Among other things, this could mean that you did not authenticate correctly, that you are requesting an action that you do not have authorization for, that the object you are requesting does not exist, or that your request is malformed.
If you receive a status in the 500 range, this generally indicates a server-side problem. This means that we are having an issue on our end and cannot fulfill your request currently.
400 and 500 level error responses will include a JSON object in their body, including the following attributes:
Name
Type
Description
id
string
A short identifier corresponding to the HTTP status code returned. For example, the ID for a response returning a 404 status code would be “not_found.”
message
string
A message providing additional information about the error, including details to help resolve it when possible.
request_id
string
Optionally, some endpoints may include a request ID that should be provided when reporting bugs or opening support tickets to help identify the issue.
Example Error Response
HTTP/1.1 403 Forbidden { "id": "forbidden", "message": "You do not have access for the attempted action." }
Responses
When a request is successful, a response body will typically be sent back in the form of a JSON object. An exception to this is when a DELETE request is processed, which will result in a successful HTTP 204 status and an empty response body.
Inside of this JSON object, the resource root that was the target of the request will be set as the key. This will be the singular form of the word if the request operated on a single object, and the plural form of the word if a collection was processed.
For example, if you send a GET request to
/v2/droplets/$DROPLET_ID
you will get back an object with a key called “
droplet
”. However, if you send the GET request to the general collection at
/v2/droplets
, you will get back an object with a key called “
droplets
”.
The value of these keys will generally be a JSON object for a request on a single object and an array of objects for a request on a collection of objects.
Response for a Single Object
{ "droplet": { "name": "example.com" ... } }
Response for an Object Collection
{ "droplets": [ { "name": "example.com" ... }, { "name": "second.com" ... } ] }
Meta
In addition to the main resource root, the response may also contain a
meta
object. This object contains information about the response itself.
The
meta
object contains a
total
key that is set to the total number of objects returned by the request. This has implications on the
links
object and pagination.
The
meta
object will only be displayed when it has a value. Currently, the
meta
object will have a value when a request is made on a collection (like
droplets
or
domains
).
Sample Meta Object
{ ... "meta": { "total": 43 } ... }
Links & Pagination
The
links
object is returned as part of the response body when pagination is enabled. By default, 20 objects are returned per page. If the response contains 20 objects or fewer, no
links
object will be returned. If the response contains more than 20 objects, the first 20 will be returned along with the
links
object.
You can request a different pagination limit or force pagination by appending
?per_page=
to the request with the number of items you would like per page. For instance, to show only two results per page, you could add
?per_page=2
to the end of your query. The maximum number of results per page is 200.
The
links
object contains a
pages
object. The
pages
object, in turn, contains keys indicating the relationship of additional pages. The values of these are the URLs of the associated pages. The keys will be one of the following:
first
: The URI of the first page of results.
prev
: The URI of the previous sequential page of results.
next
: The URI of the next sequential page of results.
last
: The URI of the last page of results.
The
pages
object will only include the links that make sense. So for the first page of results, no
first
or
prev
links will ever be set. This convention holds true in other situations where a link would not make sense.
Sample Links Object
{ ... "links": { "pages": { "last": "https://api.digitalocean.com/v2/images?page=2", "next": "https://api.digitalocean.com/v2/images?page=2" } } ... }
Rate Limit
Requests through the API are rate limited per OAuth token. Current rate limits:
5,000 requests per hour
250 requests per minute (5% of the hourly total)
Once you exceed either limit, you will be rate limited until the next cycle starts. Space out any requests that you would otherwise issue in bursts for the best results.
The rate limiting information is contained within the response headers of each request. The relevant headers are:
ratelimit-limit
: The number of requests that can be made per hour.
ratelimit-remaining
: The number of requests that remain before you hit your request limit. See the information below for how the request limits expire.
ratelimit-reset
: This represents the time when the oldest request will expire. The value is given in
Unix epoch time
. See below for more information about how request limits expire.
More rate limiting information is returned only within burst limit error response headers:
retry-after
: The number of seconds to wait before making another request when rate limited.
As long as the
ratelimit-remaining
count is above zero, you will be able to make additional requests.
The way that a request expires and is removed from the current limit count is important to understand. Rather than counting all of the requests for an hour and resetting the
ratelimit-remaining
value at the end of the hour, each request instead has its own timer.
This means that each request contributes toward the
ratelimit-remaining
count for one complete hour after the request is made. When that request’s timer runs out, it is no longer counted towards the request limit.
This has implications on the meaning of the
ratelimit-reset
header as well. Because the entire rate limit is not reset at one time, the value of this header is set to the time when the
oldest
request will expire.
Keep this in mind if you see your
ratelimit-reset
value change, but not move an entire hour into the future.
If the
ratelimit-remaining
reaches zero, subsequent requests will receive a 429 error code until the request reset has been reached.
ratelimit-remaining
reaching zero can also indicate that the “burst limit” of 250 requests per minute limit was met, even if the 5,000 requests per hour limit was not. In this case, the 429 error response will include a
retry-after
header to indicate how long to wait (in seconds) until the request may be retried.
You can see the format of the response in the examples.
Note:
The following endpoints have special rate limit requirements that are independent of the limits defined above.
Only 10
GET
requests to the
/v2/account/keys
endpoint to list SSH keys can be made per 60 seconds.
Only 5 requests to any and all
v2/cdn/endpoints
can be made per 10 seconds. This includes
v2/cdn/endpoints
,
v2/cdn/endpoints/$ENDPOINT_ID
, and
v2/cdn/endpoints/$ENDPOINT_ID/cache
.
Only 50 strings within the
files
json struct in the
v2/cdn/endpoints/$ENDPOINT_ID/cache
payload
can be requested every 20 seconds.
Sample Rate Limit Headers
... ratelimit-limit: 1200 ratelimit-remaining: 1193 rateLimit-reset: 1402425459 ...
Sample Rate Limit Headers When Burst Limit is Reached:
... ratelimit-limit: 5000 ratelimit-remaining: 0 rateLimit-reset: 1402425459 retry-after: 29 ...
Sample Rate Exceeded Response
429 Too Many Requests { id: "too_many_requests", message: "API Rate limit exceeded." }
Curl Examples
Throughout this document, some example API requests will be given using the
curl
command. This will allow us to demonstrate the various endpoints in a simple, textual format.
These examples assume that you are using a Linux or macOS command line. To run these commands on a Windows machine, you can either use cmd.exe, PowerShell, or WSL:
For cmd.exe, use the
set VAR=VALUE
syntax
to define environment variables, call them with
%VAR%
, then replace all backslashes (
\
) in the examples with carets (
^
).
For PowerShell, use the
$Env:VAR = "VALUE"
syntax
to define environment variables, call them with
$Env:VAR
, then replace
curl
with
curl.exe
and all backslashes (
\
) in the examples with backticks (
`
).
WSL is a compatibility layer that allows you to emulate a Linux terminal on a Windows machine. Install WSL with our
community tutorial
, then follow this API documentation normally.
The names of account-specific references (like Droplet IDs, for instance) will be represented by variables. For instance, a Droplet ID may be represented by a variable called
$DROPLET_ID
. You can set the associated variables in your environment if you wish to use the examples without modification.
The first variable that you should set to get started is your OAuth authorization token. The next section will go over the details of this, but you can set an environmental variable for it now.
Generate a token by going to the
Apps & API
section of the DigitalOcean control panel. Use an existing token if you have saved one, or generate a new token with the “Generate new token” button. Copy the generated token and use it to set and export the TOKEN variable in your environment as the example shows.
You may also wish to set some other variables now or as you go along. For example, you may wish to set the
DROPLET_ID
variable to one of your Droplet IDs since this will be used frequently in the API.
If you are following along, make sure you use a Droplet ID that you control so that your commands will execute correctly.
If you need access to the headers of a response through
curl
, you can pass the
-i
flag to display the header information along with the body. If you are only interested in the header, you can instead pass the
-I
flag, which will exclude the response body entirely.
Set and Export your OAuth Token
export DIGITALOCEAN_TOKEN=your_token_here
Set and Export a Variable
export DROPLET_ID=1111111
Parameters
There are two different ways to pass parameters in a request with the API.
When passing parameters to create or update an object, parameters should be passed as a JSON object containing the appropriate attribute names and values as key-value pairs. When you use this format, you should specify that you are sending a JSON object in the header. This is done by setting the
Content-Type
header to
application/json
. This ensures that your request is interpreted correctly.
When passing parameters to filter a response on GET requests, parameters can be passed using standard query attributes. In this case, the parameters would be embedded into the URI itself by appending a
?
to the end of the URI and then setting each attribute with an equal sign. Attributes can be separated with a
&
. Tools like
curl
can create the appropriate URI when given parameters and values; this can also be done using the
-F
flag and then passing the key and value as an argument. The argument should take the form of a quoted string with the attribute being set to a value with an equal sign.
Pass Parameters as a JSON Object
curl -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \ -H "Content-Type: application/json" \ -d '{"name": "example.com", "ip_address": "127.0.0.1"}' \ -X POST "https://api.digitalocean.com/v2/domains"
Pass Filter Parameters as a Query String
curl -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \ -X GET \ "https://api.digitalocean.com/v2/images?private=true"
Cross Origin Resource Sharing
In order to make requests to the API from other domains, the API implements Cross Origin Resource Sharing (CORS) support.
CORS support is generally used to create AJAX requests outside of the domain that the request originated from. This is necessary to implement projects like control panels utilizing the API. This tells the browser that it can send requests to an outside domain.
The procedure that the browser initiates in order to perform these actions (other than GET requests) begins by sending a “preflight” request. This sets the
Origin
header and uses the
OPTIONS
method. The server will reply back with the methods it allows and some of the limits it imposes. The client then sends the actual request if it falls within the allowed constraints.
This process is usually done in the background by the browser, but you can use curl to emulate this process using the example provided. The headers that will be set to show the constraints are:
Access-Control-Allow-Origin
: This is the domain that is sent by the client or browser as the origin of the request. It is set through an
Origin
header.
Access-Control-Allow-Methods
: This specifies the allowed options for requests from that domain. This will generally be all available methods.
Access-Control-Expose-Headers
: This will contain the headers that will be available to requests from the origin domain.
Access-Control-Max-Age
: This is the length of time that the access is considered valid. After this expires, a new preflight should be sent.
Access-Control-Allow-Credentials
: This will be set to
true
. It basically allows you to send your OAuth token for authentication.
You should not need to be concerned with the details of these headers, because the browser will typically do all of the work for you.
1-Click Applications
2 endpoints
Account
1 endpoint
Actions
2 endpoints
Add-Ons
8 endpoints
Apps
38 endpoints
Billing
8 endpoints
Block Storage
9 endpoints
Block Storage Actions
4 endpoints
BYOIP Prefixes
6 endpoints
CDN Endpoints
6 endpoints
Certificates
4 endpoints
Container Registries
19 endpoints
Container Registry
18 endpoints
Databases
71 endpoints
Dedicated Inference
13 endpoints
Domain Records
6 endpoints
Domains
4 endpoints
Droplet Actions
4 endpoints
Droplet Autoscale Pools
8 endpoints
Droplets
19 endpoints
Firewalls
11 endpoints
Floating IP Actions
3 endpoints
Floating IPs
4 endpoints
Functions
13 endpoints
GradientAI Platform
119 endpoints
Image Actions
3 endpoints
Images
9 endpoints
Kubernetes
28 endpoints
Load Balancers
10 endpoints
Monitoring
72 endpoints
NFS
11 endpoints
NFS Actions
1 endpoint
Organizations
2 endpoints
Partner Network Connect
9 endpoints
Project Resources
4 endpoints
Projects
9 endpoints
Regions
1 endpoint
Reserved IP Actions
3 endpoints
Reserved IPs
4 endpoints
Reserved IPv6
4 endpoints
Reserved IPv6 Actions
1 endpoint
Security
10 endpoints
Sizes
1 endpoint
Snapshots
3 endpoints
Spaces Keys
6 endpoints
SSH Keys
5 endpoints
Tags
6 endpoints
Uptime
11 endpoints
Vector Databases
11 endpoints
VPC NAT Gateways
5 endpoints
VPC Peerings
5 endpoints
VPCs
10 endpoints
In this article...
Requests
HTTP Statuses
Example Error Response
Responses
Response for a Single Object
Response for an Object Collection
Meta
Sample Meta Object
Links & Pagination
Sample Links Object
Rate Limit
Sample Rate Limit Headers
Sample Rate Limit Headers When Burst Limit is Reached:
Sample Rate Exceeded Response
Curl Examples
Set and Export your OAuth Token
Set and Export a Variable
Parameters
Pass Parameters as a JSON Object
Pass Filter Parameters as a Query String
Cross Origin Resource Sharing
Company
About
Careers
Blog
Docs
Docs Home
API Reference
CLI Reference
Release Notes
llms.txt
Trust Platform
Community
Tutorials
Q&A
Write for DOnations
Currents Research
Legal
Code of Conduct
Support
Support Center
Report Abuse
© 2026 DigitalOcean, LLC. All rights reserved
We can't find any results for your search.
Try using different keywords or simplifying your search terms.
