Skip to main content
Enneo itself is not the leading system for the contract and customer master data but retrieves this data in real-time via an API from their primary data system, such as an ERP or CRM system. This is done via 4 API calls that need to be implemented.
  • A: Retrieving a contract by contract ID: This is used when Enneo needs the current data for a specific contract. The input is the contract number, from your API the contract data (name, address, etc.) is expected.
  • B: Retrieving a customer by customer ID: This allows the reloading of the latest customer data if a contract is updated. The input is the customer number, from your API the customer data (name, associated contract numbers, etc.) is expected.
  • C: Searching for contracts based on characteristics: This is used when Enneo’s AI extracts certain data (e.g. name, address, meter number, email) from an email and needs to identify suitable contracts. Enneo expects as a response the suitable customer/contract and (optionally) a degree of legitimization.
  • D: Searching for contracts based on free text: This is used when an agent searches for contracts via the search field. The API should support search queries by name, email or other relevant data.
Each of these 4 API calls has a fixed data format that is passed, and also expects a fixed data format. Data structures with sample implementation:
The more data provided, the better Enneo’s AI works.