The Set Device API is used to associate a device ID to a specific asset_id / test_id. Typically, this is a remote probe.
ZetaSafe don’t actually keep the remote device ID, its POSTed to whichever remote system requires the ID. The remote system contacted is based on the device type value.
A valid x-Auth-token header, belonging to the user adding the device is required.
URI
Development
Production
Method
POST
Content Type
application/json
Body
Required Fields: device_id, deviceType, test_id, asset_id, client_id
{"device_id":"text", "deviceType":"text", "test_id":1234, "asset_id":2345, "client_id":5432}
An additional option value testresult_id is optional, but can be provided
Responses:
200: Device Information Received
400: Bad Request - an explanation is returned
{"result":"FOREIGN_KEY_INVALID",
"headings":[{"key":"ok","value":"OK"}],
"title":"Record not found",
"message":"The Asset with an ID value of 2004009726 could not be found."}
401: User unable to see this client
500: Error with the internal process of adding an asset.