DigitalOcean API

Name: DigitalOcean API API
Brand: DigitalOcean API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputebearer290 EndpointsREST

For Agents

Provision Droplets, manage Kubernetes clusters, configure load balancers, and deploy apps on DigitalOcean. Covers compute, networking, storage, databases, and platform services across 14 regions.

Quickstart

Get started with DigitalOcean API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a cloud server on DigitalOcean"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DigitalOcean API API.

Provision Droplets with specified sizes, images, and SSH keys across 14 datacenter regions

Deploy and scale Kubernetes clusters with configurable node pools and auto-upgrade policies

Configure managed databases (PostgreSQL, MySQL, Redis, MongoDB) with automated backups and failover

Set up load balancers with health checks, forwarding rules, and TLS termination

GET STARTED

Start building with DigitalOcean API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DigitalOcean API API for, with concrete tasks.

★ AI Agent Infrastructure Provisioning

AI agents use the DigitalOcean API through Jentic to provision cloud infrastructure on demand. An agent searches for the Droplet creation operation, receives the request schema with size, image, region, and SSH key parameters, then executes the call. DigitalOcean provisions the Droplet in under 60 seconds, returning an IP address ready for deployment. The flat pricing model (starting at $4/month) makes cost prediction straightforward for automated scaling decisions.

Create a s-2vcpu-4gb Droplet named 'web-server-01' with Ubuntu 22.04 image in the nyc1 region and attach SSH key ID 12345

Managed Kubernetes Deployment

Create and manage Kubernetes clusters with configurable node pools, automatic version upgrades, and built-in container registry integration. The API handles control plane provisioning, node scaling, and kubeconfig generation. Clusters deploy in under 5 minutes with options for high-availability control planes and multiple node pools with different Droplet sizes for mixed workload requirements.

Create a Kubernetes cluster named 'production' in sfo3 with version 1.28, a node pool of 3 s-4vcpu-8gb nodes, and auto-upgrade enabled

Managed Database Provisioning

Deploy managed database clusters with automated backups, point-in-time recovery, standby nodes, and connection pooling. Supports PostgreSQL, MySQL, Redis, and MongoDB with configurable engine versions and cluster sizes. The API manages the full database lifecycle including scaling, maintenance windows, user management, and read replica configuration without manual database administration.

Create a managed PostgreSQL 15 database cluster named 'app-db' with db-s-2vcpu-4gb size, 2 nodes, and automatic daily backups in the nyc1 region

App Platform Continuous Deployment

Deploy web applications, APIs, static sites, and background workers from GitHub or GitLab repositories with automatic builds and zero-downtime deployments. App Platform detects the runtime from source code, builds the container, and routes traffic through a global CDN. The API supports rollbacks, deployment cancellation, and per-component log retrieval for debugging failed deployments.

Create an App Platform app from GitHub repository 'myorg/web-app' with the main branch, auto-deploy enabled, and a single web component with 1 instance

Network Security Configuration

Define firewall rules, configure VPC networks, and set up load balancers to secure and distribute traffic across cloud resources. Firewalls support inbound and outbound rules by port, protocol, and source (IP ranges, Droplet tags, or load balancers). VPCs isolate resources within private networks, and load balancers distribute traffic with health checks and sticky sessions.

Create a firewall named 'web-firewall' allowing inbound TCP on ports 80 and 443 from any source, and SSH on port 22 from IP 203.0.113.0/24 only

Key Endpoints

290 endpoints — provision and manage cloud infrastructure including droplets, kubernetes clusters, managed databases, block storage, load balancers, and app platform deployments across 14 global datacenter regions.

METHOD

PATH

DESCRIPTION

POST

/v2/droplets

Create one or more new Droplets

GET

/v2/droplets

List all Droplets in the account

POST

/v2/kubernetes/clusters

Create a new Kubernetes cluster

POST

/v2/databases

Create a managed database cluster

POST

/v2/apps

Create a new App Platform application

POST

/v2/load_balancers

Create a new load balancer

POST

/v2/firewalls

Create a new firewall with rules

GET

/v2/domains/{domain_name}/records

List DNS records for a domain

POST

/v2/droplets

Create one or more new Droplets

GET

/v2/droplets

List all Droplets in the account

POST

/v2/kubernetes/clusters

Create a new Kubernetes cluster

POST

/v2/databases

Create a managed database cluster

POST

/v2/apps

Create a new App Platform application

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DigitalOcean personal access tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped Bearer tokens — raw API tokens never enter the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'create a cloud server with 4GB RAM') and Jentic returns matching DigitalOcean operations with their full schemas, including valid size slugs, region codes, and image identifiers.

Time to first call

Direct DigitalOcean integration: 1-2 days for API client setup, token management, and error handling. Through Jentic: under 1 hour — search for the operation, receive the schema, execute with automatic authentication.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Linode API

Linode offers similar Linux-focused compute with comparable pricing but fewer managed services

Choose Linode when the user prefers Akamai's network or needs specific Linode instance types. Choose DigitalOcean for broader managed services (App Platform, managed databases, Kubernetes) and a simpler API structure.

Alternative

Render API

Render focuses on PaaS deployment while DigitalOcean offers full IaaS plus PaaS

Choose Render for zero-config web service deployment from Git. Choose DigitalOcean when you need both IaaS (Droplets, networking) and PaaS (App Platform) in one account.

Complementary

Netlify API

Netlify handles static site deployment and CDN while DigitalOcean manages backend infrastructure

Use Netlify alongside DigitalOcean when deploying a JAMstack application — Netlify for the frontend CDN and DigitalOcean for backend APIs and databases.

FAQs

Specific to using DigitalOcean API API through Jentic.

What authentication does the DigitalOcean API use?

The DigitalOcean API uses Bearer token authentication. Generate a personal access token from the DigitalOcean control panel and pass it in the Authorization header as 'Bearer {token}'. Through Jentic, your token is stored encrypted in the MAXsystem vault and agents receive scoped access without handling raw tokens.

Can I create a Droplet with a specific SSH key through the DigitalOcean API?

Yes. The POST /v2/droplets endpoint accepts an ssh_keys array with SSH key IDs or fingerprints. First upload your key via POST /v2/account/keys, then reference the returned ID when creating the Droplet. The key is injected into the root user's authorized_keys on first boot.

What are the rate limits for the DigitalOcean API?

The API allows 5,000 requests per hour and 250 requests per minute per OAuth token. Rate limit headers (ratelimit-limit, ratelimit-remaining, ratelimit-reset) are included in every response. Special limits apply to specific endpoints: 12 floating IP creates per minute, 10 SSH key list requests per minute, and 5 CDN requests per 10 seconds.

How do I deploy a Kubernetes cluster using the DigitalOcean API through Jentic?

Search Jentic for 'create kubernetes cluster DigitalOcean'. The agent receives the POST /v2/kubernetes/clusters schema requiring name, region, version, and node_pools array. Each node pool specifies size (e.g., 's-4vcpu-8gb'), count, and name. The cluster provisions in under 5 minutes with kubeconfig available via a separate endpoint.

Can I manage DNS records for my domain through the API?

Yes. Use POST /v2/domains to register a domain, then POST /v2/domains/{domain_name}/records to create A, AAAA, CNAME, MX, TXT, NS, and SRV records. Each record requires type, name, data, and optional TTL. The GET endpoint lists all existing records for zone management.

How does Jentic help AI agents manage DigitalOcean infrastructure?

Agents search by intent (e.g., 'provision a web server') and Jentic returns matching DigitalOcean operations with full request schemas. The agent fills in Droplet size, region, and image parameters, then executes. No SDK installation or token management required — install with pip install jentic and sign up at https://app.jentic.com/sign-up.