GLPI Rest APIInstall

Summary

Creates a new Assistance Management item (Ticket, Change, or Problem) in GLPI via the REST API.

Inputs

• itemtype (required) — Type of Assistance Management item to create. Determines which status field is shown and which GLPI endpoint is used (Ticket, Change, or Problem). Accepts the value of Ticket, Change, or Problem. Default is Ticket.
• title (required) — Title of the item. Sent as the 'name' field in the payload.
• description (required) — Content/description of the item. Sent as the 'content' field in the payload.
• status_ticket — Status of the ticket. Visible and used when itemtype is Ticket. Options: New (1), Processing (Assigned) (2), Processing (Planned) (3), Pending (4), Solved (5), Closed (6). Default is 1 (New).
• status_problem — Status of the problem. Visible and used 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 is 1 (New).
• status_change — Status of the change. Visible and used when itemtype is Change. Options: New (1), Pending (4), Solved (5), Closed (6), Accepted (7), Review (8). Default is 1 (New).
• users_id_requester — User ID or email address of the requester. Sent as _users_id_requester when provided.
• users_id_assign — User ID to assign the item to. Sent as _users_id_assign when greater than 0. Default is 0 (no assignment).
• options — Additional optional fields for the created item. Contains sub‑options described below.
• options.itilcategories_id — Category ID to associate with the item. Sent as itilcategories_id. Default is 0 (no category).
• options.users_id_observer — User ID or email address of an observer. Sent as _users_id_observer when provided.

Output shape

array

The node returns an array containing a single object per executed item. Each object holds the JSON response from GLPI's POST /apirest.php/{ItemType} request, which typically includes the created item's ID and other fields (e.g., name, content, status).

Examples

Example 1: Create a new Ticket with title, description, and assign it to a user.

Set itemtype to Ticket, provide Title and Description, optionally set users_id_assign to the desired user ID, and leave other fields at defaults.