The Edit Asset API allows you to edit an existing ZetaSafe asset. You will need the ZetaSafe Asset PK (Primary Key).
You may not change the Asset Type in this API. You must use the Change Asset Type API.
If you don’t provide an existing ZetaSafe Asset PK, or provide an invalid ZetaSafe Asset PK, or provide a valid ZetaSafe Asset PK for a different Client, the request will be rejected.
A valid x-Auth-token header, belonging to the user editing the asset is required. This token must be related to the ZetaSafe Client in which the asset resides.
URI
Development
Production
Method
POST
Content Type
application/json
Body
Required Fields:
{"id":"105167335300"}
id is the ZetaSafe Asset PK
All Fields Edit Asset Example
{
"assetId":"###",
"locationId":"###",
"barcode":"###",
"assetDescription":"###",
"assetIdentifier":"###",
"assetStatus":"###",
"barcode":"###",
"groupCode1":"###",
"groupCode2":"###",
"name":"###",
"longitude":"###",
"latitude":"###",
"altitude":"###",
"rfid":"###",
"riskrating":"###",
"attributes":[
{"id1":"value1","id2":"value2"}
]
}
name = secondary identifier
attributes.id field is ALWAYS the definition_id
Responses:
200: Success
400: Bad Request - an explanation is returned
403: Unauthorised/Access Denied
{
"timestamp": 1555322863458,
"status": 403,
"error": "Forbidden",
"message": "Access Denied",
"path": "/v1/note/advanced/handheld/add"
}
404: Asset not found
409: Duplicate Entries
This may occur if you attempt to add an asset to ZetaSafe which contains a barcode which is already assigned to another asset within the same Client.
500: Error with the internal process of editing an asset.