Introduction
Welcome to the Druva developer hub. This page will help you get started with Druva APIs. You will find comprehensive guides and documentation to help you start working with Druva APIs as quickly as possible, as well as reference data and support if you get stuck.
Let's start developing!
The Getting Start Guide provides the background information developers need to successfully integrate with Druva products. Understanding how to access the APIs, develop appropriate security measures, and properly structure API requests and responses are all found in this guide.
We recommend familiarizing yourself with the content before you begin to use the APIs.
Druva APIs are built around REST and support the following:
- JSON formatted requests and responses
- Standard HTTP Verbs/Methods
- Standard HTTP Error Codes
Integration Workflow
Important
The following integration workflow is applicable to -
- Endpoints and Data Governance
- Hybrid Workloads
- Cyber Resilience
Administrator Account Required for integrating using APIs
- For integrating with Endpoints and Data Governance APIs, you must be a Druva Cloud Administrator.
- For integrating with Hybrid Workloads or Cyber Resilience APIs, both, Druva Cloud Administrator and Product Administrator can perform the integration.
For Endpoints and Data Governance GovCloud, Hybrid Workloads GovCloud, and Native Workloads see the respective section for instructions.
The following steps are involved in API integration:
- Create API Credentials from the Druva Cloud Platform Console
- Encode the API Credentials to Base64
- Request and receive Access Token using the Base64 encoded API Credentials
- Use the Access Token to make API calls.
API credentials can be created and managed from Druva Cloud Platform Console. Refer Create and Manage API Credentials to learn API credentials management.
Security
All the API requests must be made over HTTPS. API requests made over plain HTTP will fail. Unauthenticated API calls will also fail.
Important
The API Credentials which is a combination of the Client ID and Secret Key are equivalent to user name and password. One can access all the Druva APIs and in turn, access the data stored within Druva products. It is strongly recommended not to share the Client ID and Secret Key with unauthorized sources.
Updated 6 months ago