REST API - Update a CI
Last modified on 2022/11/08 13:22
Contents
PUT /assets/{ci_id}
- This method allows a specified configuration item (CI) to be modified.
example /assets/9479
Notes
See Service Manager REST API Conventions.
- You must supply a table in JSON format in the body of the HTTP request.
- If successful, an HTTP status code 201 is returned and a URL link (HREF) to the updated resource is provided.
CommonNotes_JSONandFields
JSON Format / Field Format:
- The field names are those of the Service Manager.data model.
example available_field_1
- To update a field, respect the following JSON format: "field_name":"value".
- JSON object names, including those representing Service Manager database fields, are not case sensitive.
example field_name, Field_Name and FIELD_NAME are equivalent
List of parameters / fields
Mandatory parameters
- You must use the parameter below in the URL.
- You must use at least one of the optional fields in the body of the HTTP request. Otherwise an error is returned.
| Parameter | Type | Description / Example |
|---|---|---|
| ci_id | integer | CI identifier |
Optional parameters
None
Optional fields
- You can use all the fields from the AM_ASSET table in the body of the HTTP request.
- In addition to the fields provided by EasyVista, you can also assign values to the fields which you have added to the Service Manager database. These are fields with the prefix e_.
example e_field_name_xyz
HTTP status codes for the method
StatusHeader
| Code | Error | Description |
|---|
Status201
| 201 | Created | Request successfully processed and element created. |
Status401
| 401 | Unauthorized | Incorrect authentication process for accessing the resource: Incorrect login/password, invalid session, incorrect Service Manager account.
example { "error": "Invalid Login / Password" } |
Status405
| 405 | Method not allowed | Unauthorized request method, i.e. it is not supported or not appropriate for the resource.
example { "error": "Invalid input parameter" } |
Examples
Example of the body of an HTTP request
{
"asset_label": "New CI via REST API - Updated",
"purchase_price": "2 000,00",
"automatic_renewal": "",
"estimated_percentage_use": "90",
"installation_date": "21/05/2019",
"available_field_1": "Available for custom use - Updated",
"comment_asset": "You can even update the comment update"
}
"asset_label": "New CI via REST API - Updated",
"purchase_price": "2 000,00",
"automatic_renewal": "",
"estimated_percentage_use": "90",
"installation_date": "21/05/2019",
"available_field_1": "Available for custom use - Updated",
"comment_asset": "You can even update the comment update"
}
Result with a status code 201 returned
{
"HREF": "https://{your_server}/api/v1/{your_account}/assets/9504"
}
"HREF": "https://{your_server}/api/v1/{your_account}/assets/9504"
}
ConventionsAPI
REST API Conventions
| Convention | Meaning | |
|---|---|---|
| Orange | Parameters used in an HTTP request string which do not correspond to Service Manager database fields.
example Method View a list of assets https://{your_server}/api/v1/{your_account}/assets?max_rows=3&fields=asset_tag |
|
| Black and Bold | Parameters used in the URL of an HTTP request which correspond to Service Manager database fields.
example Method View an asset https://{your_server}/api/v1/{your_account}/assets/{asset_id} |
|
| Green | Parameters used in the body of an HTTP request which represent JSON object names corresponding to Service Manager database fields; they allow the value of a database field to be assigned or modified.
example Method Close an incident/request { "closed": { "end_date": "11/20/2016 12:12:12", } } |
|
| Parameters used in the body of an HTTP request which represent JSON object names not corresponding to Service Manager database fields.
example Method Reopen an incident/request { "restarted": { "comment": "string (required)" } } |
||