Updates a Slot Filler from a Flow.
Supply the API Key in the HTTP-Header
The Accept header specifies the media type that the client expects in the response. Available options: application/json, application/hal+json, application/xml, text/xml, text/csv. The default value is application/json.
application/json, application/hal+json, application/xml, text/xml, text/csv The unique identifier for the Flow.
24^[a-z0-9]{24}$The unique identifier for the Slot Filler.
24^[a-z0-9]{24}$The payload for creating or updating a Slot Filler.
The display name of the Slot Filler.
The type of the Slot Filler.
age, date, duration, email, intent, slot, money, number, percentage, regex, temperature "age"
If set to true, extracts only Slots from predefined Keyphrases.
If set to true, stores the result in the Context object.
The key used to store the result in the Context object.
If set to true, the result is stored in the Contact Profile.
The key used to store the result in the Contact Profile.
If set to true, stores metadata about the extracted Slot.
If set to true, the user input isn't checked for the Slot that is already in the Context object.
The additional validation expression or script.
Determines where to extract the Slot value from. By default, the Slot value is extracted from the user input. You can set a CognigyScript expression in this parameter to override the detected Slot value with a value from the Input, Context, or Profile objects. This parameter works only if the user input is recognized and the CognigyScript expression doesn't resolve to a falsy value.
The regex pattern to extract specific data from the user input. Used only when the Slot Filler type is regex.
Specifies which Slot this Filler is associated with, for example, date or airport_code. Used only when the Slot Filler type is slot.
Successfully updated SlotFiller