Create device mapping

post

https://apis.druva.com/insync/endpoints/v1/devicemappings

Creates a secure user-to-device mapping to perform a mass deployment in a non-AD/LDAP environment or perform bulk replace of devices. The user-to-device mapping ensures controlled device and user activation of inSync client and prevents addition of rogue or unauthorized devices to inSync.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

emailID

string

required

Specify the email address of the user. Example - [email protected]

userName

string

required

Specify the username of the user in Druva inSync. Example - Ernie Carter

deviceName

string

required

Specify the name of the device that is registered with the user. Example - Ernie Carter's Macbook

deviceIdentifierType

string

enum

required

Specify the unique device identifier type of the device.(serial-number, uuid, or hostname)

Allowed:

deviceIdentifier

string

required

Specify the unique device identifier for the selected type. (serial-number, uuid, or hostname).

oldDeviceName

string

Name of the user's old device in Druva inSync that is to be replaced with a new device.

Note: Specify the value for this parameter only if you want to replace the device for the user, else keep this field blank.

restoreData

string

enum

The type of data restore to be performed.(ALL, SYSTEM, OR DATA) Type of data to be restored on the new device.Specify one of the following value:

All - To restore both, the data and the system settings from the existing device on the new device.
SYSTEM - To restore only the system settings from the existing device on the new device. 3)DATA - To restore only the data from the existing device on the new device.

Note: Specify the value for this parameter only if you want to replace the device for the user, else keep this field blank.

Allowed:

Responses

400

Bad Request

401

The request did not include an authentication token or an expired authentication token was supplied.

404

The requested resource was not found.

422

The request was well-formed but was not processed due to semantic errors.

200OK

500The request was not processed due to an internal error in inSync Cloud.

501Requested HTTP method is not implemented.