Introduction

​

enneo API Documentation

The enneo API provides a set of endpoints for importing/manipulation of 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.

You find the full API specification in swagger format here, including data structures, return formats and examples. This is great for developers.

​

Importing/Manipulation of Tickets

The enneo API allows you to import and manipulate tickets. You can create new tickets, update existing ones, and retrieve ticket information. The endpoints available for ticket management include:

• 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

Tags provide a way to categorize and organize data in the enneo system. The API allows you to manage tags by creating, updating, and retrieving tag information. Tags can be skills, 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 by ID

​

ERP Interaction

The enneo API also supports integration with ERP systems, allowing you to search and retrieve customer information. The following endpoint is available for 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 coming from the authorization microservice. Please refer to these docs for further information: