GLPI REST API

Name: GLPI REST API
Brand: GLPI REST API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsProject ManagementapiKey, basic22 EndpointsREST

For Agents

Manage GLPI tickets, computers, and any GLPI item type through a generic REST surface with session-token auth on a self-hosted GLPI instance.

Connect the GLPI REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GLPI REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GLPI REST API.

Open and close an authenticated GLPI session via initSession and killSession

Create, read, update, and delete any GLPI item type (Ticket, Computer, User, etc.) via the generic /{itemtype} endpoints

Search GLPI items with criteria via /search/{itemtype} and discover available filters via /listSearchOptions/{itemtype}

Fetch related sub-items for an item (e.g. Ticket_User attached to a Ticket) via /{itemtype}/{id}/{subItemtype}

GET STARTED

Start building with GLPI REST API

Explore with Jentic

View OpenAPI Document

GLPI is an open-source IT asset management and helpdesk platform used to track computers, network devices, software, contracts, and support tickets. The GLPI REST API exposes that catalogue programmatically through a small set of generic endpoints: a session lifecycle (initSession, killSession, profile and entity switching) and a generic CRUD surface that operates on any GLPI item type via /{itemtype}, /{itemtype}/{id}, and the search endpoints. That keeps the surface compact while giving access to the full GLPI data model.

Use Cases

Patterns agents use GLPI REST API for, with concrete tasks.

★ Help-Desk Ticket Automation

IT teams running GLPI can replace email-only inboxes with API-driven ticket creation: a chatbot or monitoring tool POSTs to /Ticket via the generic /{itemtype} endpoint and updates the ticket status as the issue is investigated. Combined with /search/Ticket for backlog views, this turns GLPI into the system of record for a fully automated triage flow. Setup is typically a day, including app-token provisioning.

POST /Ticket with {name, content, urgency} after initSession, then capture the returned ticket ID and store it on the originating alert.

IT Asset Inventory Sync

Discovery tools that scan the network can keep the GLPI Computer inventory in sync by upserting Computer items via POST /Computer and PATCHing existing records by ID. The /search/Computer endpoint backs reporting, and /listSearchOptions/Computer surfaces every searchable field so the integration code does not have to be hard-coded against GLPI's internal numeric option IDs.

After initSession, POST /Computer for each scanned host and PUT /Computer/{id} for any existing record whose serial number matches.

Agent-Assisted Service Desk

An AI agent through Jentic can resolve common service desk requests by searching for the user's open tickets via /search/Ticket, summarising the latest status, and either updating the ticket or creating a new one. Because GLPI's CRUD is generic, the same flow works for change requests, problems, or any other supported item type.

Search Jentic for 'list glpi tickets', load the schema for GET /search/{itemtype}, and execute with itemtype=Ticket and criteria for status open.

Key Endpoints

22 endpoints — glpi is an open-source it asset management and helpdesk platform used to track computers, network devices, software, contracts, and support tickets.

METHOD

PATH

DESCRIPTION

GET

/initSession

Open an authenticated session

GET

/{itemtype}

List items of a type

POST

/{itemtype}

Create one or more items

PUT

/{itemtype}/{id}

Update an item by ID

DELETE

/{itemtype}/{id}

Delete an item by ID

GET

/search/{itemtype}

Search items with criteria

GET

/listSearchOptions/{itemtype}

List searchable fields for an item type

GET

/initSession

Open an authenticated session

GET

/{itemtype}

List items of a type

POST

/{itemtype}

Create one or more items

PUT

/{itemtype}/{id}

Update an item by ID

DELETE

/{itemtype}/{id}

Delete an item by ID

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

GLPI Session-Token, App-Token, and userToken values are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and the headers are injected at execution time, so the tokens never enter the agent's prompt.

Intent-based discovery

Agents search Jentic by intent ('open glpi ticket', 'list glpi computers') and Jentic returns the matching generic /{itemtype} or /search/{itemtype} operation with its schema, hiding the GLPI-specific numeric search-option IDs behind named parameters.

Time to first call

Direct GLPI integration: 1-2 days for session lifecycle, header juggling, and search-option discovery. Through Jentic: under an hour - search, load, execute.

FAQs

Specific to using GLPI REST API through Jentic.

What authentication does the GLPI REST API use?

GLPI requires a Session-Token plus an App-Token, both sent as headers. You obtain the Session-Token by calling /initSession with either basicAuth credentials or a userTokenAuth Authorization header. Through Jentic both tokens are stored in the vault and injected per call.

Can I create and update any GLPI item type with this API?

Yes. The /{itemtype} endpoints are generic - itemtype is a path parameter that resolves to Ticket, Computer, User, ContractItem, and any other GLPI class. POST creates, PUT updates, DELETE removes, and GET reads or lists.

What are the rate limits for the GLPI REST API?

GLPI is self-hosted, so there is no provider-imposed rate limit; throughput depends on the host's PHP and database tuning. For bulk syncs use /getMultipleItems and batched POSTs to /{itemtype} rather than individual calls per record.

How do I list open tickets through Jentic?

Search Jentic for 'glpi search items', load the schema for GET /search/{itemtype}, and execute with itemtype=Ticket and the appropriate status criteria. Run pip install jentic to start.

How do I discover the searchable fields for an item type?

Call GET /listSearchOptions/{itemtype} - the response is the canonical list of numeric field IDs and labels that /search/{itemtype} accepts as criteria, removing the need to hard-code field numbers.

Is the GLPI API free?

Yes. GLPI itself is open source and self-hosted, so the API is free to call against any GLPI instance you operate. Hosted GLPI providers may charge for the underlying instance but not per API call.

GLPI REST API

Connect the GLPI REST API to your agent

Capabilities

Start building with GLPI REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs