Druva
Druva is a cloud data protection and management platform providing SaaS backup, disaster recovery, and data governance for endpoints, data centers, and SaaS applications. Druva exposes a public REST API across its Cyber Resilience, Endpoint Data Governance, Enterprise Workloads, CloudRanger, MSP, and Legal Hold products, using token-based authentication and JSON over HTTPS.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Druva the way a machine reads it — 22 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Druva scores 45.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Druva
Each block below is one kind of artifact we hold for Druva. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Druva Cyber Resilience API
The Druva Cyber Resilience REST API provides programmatic access to reports and events across the Druva Data Resiliency Cloud, supporting ransomware recovery, anomaly detection,...
Druva Endpoints and Data Governance API
The Druva Endpoints and Data Governance API exposes Reports and Events endpoints for visibility into endpoint backups, user activity, and governance posture across managed devic...
Druva Enterprise Workloads API
The Druva Enterprise Workloads Events API provides programmatic access to events generated across protected enterprise workloads such as servers, virtual machines, and databases...
Druva CloudRanger Native Workloads API
The Druva CloudRanger Native Workloads API provides automated backup, disaster recovery, and lifecycle management for AWS-native workloads including EC2, EBS, RDS, Redshift, and...
Druva MSP API
The Druva MSP API enables managed service providers to programmatically manage tenants, customers, and reporting across the Druva platform from a single MSP console integration.
Druva Legal Hold Targeted Download API
The Druva Legal Hold Targeted Download API supports legal and compliance teams in initiating targeted downloads of preserved data from devices placed under legal hold within Druva.
Druva Accounts API
The Accounts API from Druva — 2 operation(s) for accounts.
Druva Authentication API
The Authentication API from Druva — 1 operation(s) for authentication.
Druva Backups API
The Backups API from Druva — 1 operation(s) for backups.
Druva Cyber Resilience API
The Cyber Resilience API from Druva — 2 operation(s) for cyber resilience.
Druva Policies API
The Policies API from Druva — 2 operation(s) for policies.
Druva Reports API
The Reports API from Druva — 1 operation(s) for reports.
Druva Schedules API
The Schedules API from Druva — 1 operation(s) for schedules.
Druva Servers API
The Servers API from Druva — 1 operation(s) for servers.
Scroll within the panel for all 14 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Druva REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Druva Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Druva Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Druva Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Druva — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/druva · machine-readable index on apis.io