Enneo API Documentation
The Enneo API offers a series of endpoints for importing/manipulating tickets, user management, tag management, and ERP interaction. This documentation outlines the typical use cases and provides details on how to interact with each endpoint. The complete API specification can be found in Swagger format here, including data structures, return formats, and examples. This is ideal for developers.Importing/Manipulating Tickets
The Enneo API allows importing and manipulating tickets. New tickets can be created, existing ones updated, and ticket information can be retrieved. The available endpoints for ticket management are:-
POST /tickets: Create a new ticket -
PATCH /ticket/{id}: Update an existing ticket, e.g., by assigning contracts or changing the status -
GET /ticket/{id}: Retrieve a ticket based on its ID
Tag Management
With tags, data in the Enneo system can be categorized and organized. The API allows managing tags by creating, updating, and retrieving tag information. Tags can be capabilities, but also products or brands. The endpoints for tag management are:-
POST /tag: Create a new tag -
GET /tag: List all tags -
GET /tag/{id}: Retrieve tag information based on the ID
ERP Interaction
The Enneo API also supports integration with ERP systems, enabling the searching and retrieving of customer information. The following endpoint is available for ERP interaction:GET /erp/customers: Search and retrieve customer information
User Management
For user management, Enneo uses a different API specification that originates from the authorization microservice. Please refer to this documentation for further information:Enneo User Management API
View the OpenAPI specification file