Request and response structure

🚧

Important

If you are a Druva CloudRanger user, see Getting started with CloudRanger APIs

Request Structure

Base URL

Each URL is called a request. All requests to Druva APIs must be sent to the base URL -

Requests

To call a particular Druva product API, append the base URL with the name of the product.
Example
inSync Cloud
https://apis.druva.com/insync/
inSync GovCloud
https://govcloudapis.druva.com/insync/

The URL to call a specific endpoint will be a combination of product-specific URL appended with endpoint path.

Example: https://apis.druva.com/insync/endpoints/v1/devices

Some of the endpoints may also contain Path Parameters. Add the respective values to form the URL. To request information about a particular device that is configured with inSync with ID 123, the URL will be:

Example: https://apis.druva.com/insync/endpoints/v1/devices/123

Request Method

Druva APIs use standard HTTP Verbs/Methods. Based on the action that you are trying to perform using your script, choose an appropriate method (GET, POST, PUT, or DELETE). Refer to the Endpoint section to learn more about the methods supported for every endpoint.

Header

Druva APIs use headers for authentication and authorization. Every API call needs to pass an Access Token in the header. Refer to Authentication section to know more about generating an​ Access Token.

Body

The request body supports only JSON payloads.