apirest.php, GLPI 10.x/11) live through a Collector on your network — reading and acting on demand, with nothing stored on the Myrmex side.
What Myrmex Can Do
Manage tickets
Open, assign, follow up, pend, solve, and close tickets — with approval for changes.
Directory lookups
Resolve users, groups, and categories live when working a ticket.
Enrich
Pull a ticket’s full timeline in one shot, on demand.
Correlate
Open or update tickets from security findings, via Hydra.
Before You Start
- The REST API enabled in GLPI: in Setup → General → API, turn on the REST API (
enable_api) and login with credentials (enable_api_login_credentials). - An API client whose IP range covers your Collector — the default client is restricted to localhost. Copy its App Token if it defines one.
- A GLPI user (username + password) for the integration; its profile defines the entities and tickets it can see and change. Private credentials are supported, so operators can connect with their own GLPI account and have actions audited under their name.
- A Collector that can reach the GLPI host.
Step 1 — Create the Credential in GLPI
1
Enable the REST API
In Setup → General → API, enable the REST API and enable login with credentials.
2
Configure an API client
In the same API settings, edit the default client (or add one) and set its IPv4/IPv6 range to include your Collector. If the client defines an App Token, copy it.
3
Create the integration user
Add a GLPI user with a strong password and assign a profile scoped to the right entities and ticket permissions.
4
Record the details
Note the host, username, password, and (if set) the App Token.