Introduction

enneo API Documentation

The enneo API provides a set of endpoints for importing/manipulating tickets, user management, tag management, and ERP interaction. This documentation outlines the typical use cases and provides details on interacting with each endpoint.

The complete API specification can be found in the Swagger format here, including data structures, return formats, and examples. This is ideal for developers.

Importing/Manipulating Tickets

The enneo API allows for the import and manipulation of tickets. New tickets can be created, existing ones updated, and ticket information 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 by its ID

Tag Management

With tags, data can be categorized and organized within the enneo system. The API allows for the management of tags through the creation, update, and retrieval of tag information. Tags can be capabilities as well as 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 by its ID

ERP Interaction

The enneo API also supports the integration with ERP systems, allowing for the search and retrieval of customer information. The following endpoint is available for the ERP interaction:

• GET /erp/customers: Search and retrieve customer information

Please refer to the enneo API documentation for detailed information on request and response formats, authentication, and error handling.

User Management

For user management, enneo uses a different API specification, which comes from the authorization microservice. Please refer to this documentation for further information:

enneo User Management API

View the OpenAPI specification file