curl --request GET \
--url https://demo.enneo.ai/api/mind/settings \
--header 'Authorization: Bearer <token>'[
{
"name": "ticketingSystem",
"category": "email",
"group": "Generic E-Mail Settings",
"label": "Ticketing system in use",
"description": "Enneo supports multiple ticketing systems. Please select one.",
"type": "select",
"config": null,
"value": "internal",
"defaultValue": "internal"
}
]JWT-based authentication
Filter by name of the setting
Filter by which module uses the setting
Filter by category of the setting
Whether to show secrets in the result
List of client-specific configruation settings.
"ticketingSystem"
"email"
"Generic E-Mail Settings"
"Ticketing system in use"
"Enneo supports multiple ticketing systems. Please select one."
Format in which the FE should render this setting. Follows the enneo standard dynamic intent form options specified in Notion
text, date, radio, number, integer, checkbox, textarea, select, json, executor, executors, multiselect "select"
Additional configuration properties that are dependant on type or rarely used
Anzeigen untergeordnete attribute
If type is 'select', then this lists the dropdown options available to the user
Information that the FE should render this field as a readonly
false
Information that this is sensitive information. Value will only be returned if the user has sufficient permissions, and if the query parameter showSecrets=true was provided
false
"internal"
"internal"
curl --request GET \
--url https://demo.enneo.ai/api/mind/settings \
--header 'Authorization: Bearer <token>'[
{
"name": "ticketingSystem",
"category": "email",
"group": "Generic E-Mail Settings",
"label": "Ticketing system in use",
"description": "Enneo supports multiple ticketing systems. Please select one.",
"type": "select",
"config": null,
"value": "internal",
"defaultValue": "internal"
}
]