Update Item(s)
Update one or more existing items in ITSM-NG.Endpoint
HTTP Methods
BothPUT and PATCH are supported and behave identically for updates.
Headers
Session token obtained from initSession
Optional authorization string from API configuration
Must be
application/jsonURL Parameters
The unique identifier of the item to update. Optional if provided in the request body.
Request Body
For single item: an object with fields to updateFor multiple items: an array of objects, each containing an
id field and the fields to updateResponse
true if update succeeded, false if failedStatus message or error description
Response Codes
200 OK- Item(s) updated successfully207 Multi-Status- Bulk operation with some failures400 Bad Request- Invalid input parameters401 Unauthorized- Invalid or missing session token404 Not Found- Item not found
Update Single Item (URL ID)
Update a single item by specifying the ID in the URL.Example Request
Example Response
Update Single Item (Body ID)
Update a single item by specifying the ID in the request body.Example Request
Example Response
You can omit the ID from the URL and provide it in the
input object instead. This is useful when updating multiple items or when building generic update functions.Update Multiple Items (Bulk)
Update multiple items in a single request.Example Request
Example Response
Using PATCH Method
The PATCH method works identically to PUT.Example Request
Example Response
Special Use Cases
Lost Password Request
Request a password reset for a user account.Endpoint
Requirements
- GLPI must have notifications enabled
- The email address must belong to an existing user
Request Body
Email address of the user requesting password reset
Example Request
Example Response
Password Reset
Complete the password reset process using a reset token.Endpoint
Request Body
Email address of the user
Reset token received via email
The new password
Example Request
Example Response
Common Update Fields
Standard Fields
Update the item name
Update comments or description
Move item to different entity
Soft delete/restore the item (use DELETE endpoint for actual deletion)
Asset Fields
Update serial number
Update inventory number
Update contact person
Update location
Update state (e.g., move to Production)
Update technical manager
ITIL Fields
Update ticket/problem/change content
Update status (e.g., close ticket)
Update priority level (1-5)
Update urgency level (1-5)
Update impact level (1-5)
Partial vs. Full Updates
The API supports partial updates - you only need to include fields you want to change.Partial Update Example
Update only the serial number:Full Update Example
Update multiple fields:Error Handling
Common Errors
Unable to update the item. Check GLPI logs for details.
Some items in bulk operation failed. Check the response array for individual results.
The specified item ID does not exist.
User lacks permission to update items of this type.
Validation Errors
Updates may fail due to:- Invalid foreign keys: Referenced IDs must exist
- Business rules: Some fields have constraints (e.g., can’t reopen closed tickets)
- Locked items: Items locked by another process
- Permission issues: User profile must have update rights
Best Practices
Audit Trail: All updates are logged in GLPI’s history unless you explicitly disable it with the
history parameter.Field Omission: Fields not included in the
input object are not modified. There’s no need to send the complete object.