ticket
- POSTGet next ticket id to work on
- POSTGet a list of tickets
- POSTCreate a ticket
- PATCHUpdate a few tickets at once
- GETGet a ticket
- PATCHUpdate a ticket
- GETGet ticket variables
- GETGet a tickets history
- POSTForward a ticket
- POSTAuto-execute a ticket
- GETPing a ticket
- GETGet ticket activity
- GETGet ticket stats
- GETGet agent queue status
export
customer
intent
aiAgent
- GETList of all available AI agents as an array
- GETList of all available AI agents as an tree based on associated tag
- POSTLoad enneo default AI Agents
- POSTCreate a new aiAgent
- GETGet an AI Agent by id
- DELDelete an existing AI Agent
- PATCHUpdate an existing AI Agent
- GETGet similar tickets for an AI Agent
- POSTPreview an AI Agent
- POSTGet the outcome of an AI Agent
aiQualityCheck
- GETGet all test runs with pagination
- POSTSchedule a new AI quality check
- GETGet a specific test run by ID
- DELDelete a specific test run by ID
- PATCHUpdate the expected result of a test ticket
- PATCHAccept the expected result of a test ticket
- POSTAccept ALL the expected results of for a test run
- GETGet all AI agents for which test runs can be triggered
- GETGet all AI agents for which test runs can be triggered
- GETGet test cases by AI agent ID
- POSTAdd test cases for an AI agent
- DELDelete a test case by ID
- PATCHUpdate a test case by ID
intentTemplate
profile
team
reminder
settings
- GETGet settings of a client
- POSTUpdate multiple settings at once
- GETGet settings of a client and return the results in a compact form
- GETGet settings of a client in a grouped way for a category
- PUTUpdate setting
- GETSearch settings
- GETGet Subchannels
- POSTAdd a new Subchannel
- DELDelete a Subchannel
- GETGet User Defined Functions
- POSTAdd a new User Defined Function
- DELDelete a User Defined Function
- GETRedirect to Microsoft authorization page
- GETCallback for Microsoft authorization
tag
cron
version
knowledgeSourceStructure
knowledgeSource
telephony
cortex
settings
Search settings
settings
Search settings
Search through settings by name, description, or category
GET
/
settings
/
search
curl --request GET \
--url https://demo.enneo.ai/api/mind/settings/search
[
{
"type": "setting",
"name": "Last Agent Routing",
"description": "When enabled, a ticket will be assigned to the agent after handling. Customer responses to this ticket will then be routed to the original agent. The advantage is more effective handling, as there is no need to familiarize oneself with the case and feedback is received directly related to the inquiry. In case of absence, such tickets must be routed manually.",
"url": "/settings/category/routing#lastAgentRouting",
"relevance": 1
}
]
Authorizations
Cookie-based authentication
Query Parameters
The search term to filter settings by
Response
200
application/json
Successful operation
The response is of type object[]
.
Previous
Get SubchannelsA subchannel is a further differentiation of the channel, and is - For emails, they are the mailboxes, e.g. support@enneo.ai and sales@enneo.ai - For chat, they are the chatbots, e.g. the chatbot on the website and the chatbot on the customer portal - For voice, they are the phone numbers, e.g. the phone number for support and the phone number for sales.
Next
curl --request GET \
--url https://demo.enneo.ai/api/mind/settings/search
[
{
"type": "setting",
"name": "Last Agent Routing",
"description": "When enabled, a ticket will be assigned to the agent after handling. Customer responses to this ticket will then be routed to the original agent. The advantage is more effective handling, as there is no need to familiarize oneself with the case and feedback is received directly related to the inquiry. In case of absence, such tickets must be routed manually.",
"url": "/settings/category/routing#lastAgentRouting",
"relevance": 1
}
]