GLPI Rest API V2Install

Summary

Updates an existing GLPI Assistance Management item (Ticket, Change, or Problem) via PUT request to the v2.1 API.

Inputs

• itemtype (required) — Type of Assistance Management item: Ticket, Change, or Problem. Default: Ticket.
• itemId (required) — ID of the Assistance Management item to update. Default: 0.
• title — Title of the item. Optional.
• description — Content/Description of the item. Optional.
• status_ticket — Status of the ticket. Shown when itemtype is Ticket. Options: New(1), Processing Assigned(2), Processing Planned(3), Pending(4), Solved(5), Closed(6). Default: 1.
• status_problem — Status of the problem. Shown when itemtype is Problem. Options: New(1), Processing Assigned(2), Processing Planned(3), Pending(4), Solved(5), Closed(6), Accepted(7), Under Observation(8). Default: 1.
• status_change — Status of the change. Shown when itemtype is Change. Options: New(1), Pending(4), Solved(5), Closed(6), Accepted(7), Review(8). Default: 1.
• users_id_requester — User ID or Email of the requester. Optional.
• users_id_assign — User ID to assign the item to. Optional. Default: 0.
• options — Additional options for the item. Optional collection. Contains itilcategories_id (number, default 0) and users_id_observer (string, default '').

Output shape

The GLPI API response as a JSON object, returned as the node's execution result.

The node sends a PUT request to /api.php/v2.1/Assistance/{itemType}/{itemId} with a JSON body composed of the provided fields. The status field is populated from the first non-zero value among status_ticket, status_problem, or status_change based on the selected item type. Optional fields omitted from the body if left at default/empty.

Examples

Example 1: Update a Ticket with new title and status.

itemtype: Ticket, itemId: 42, title: 'New title', status_ticket: 5