The documentation states here that dynamic variables have a string key with any value, but anything other that an object with string keys and string values is flagged as invalid.
In other words, the following payload would be valid according to the docs, but it not actually valid.
{
“retell_llm_dynamic_variables”: {
“person”: {
“first_name”: “John”,
“last_name”: “Doe”
}
}
}
Hi,
Our docs state that it must only be in key,value string format.
**
retell_llm_dynamic_variables**
object
Add optional dynamic variables in key value pairs of string that injects into your Response Engine prompt and tool description. Only applicable for Response Engine.
If you could let me know what part of the API is confusing / contradictory, we could make adjustments on our end!
Best,
Colin
The yaml openapi spec is incorrect. It lists the type as any instead of string.
This is the existing openapi spec:
retell_llm_dynamic_variables:
type: object
additionalProperties: {}
example:
customer_name: John Doe
description: >-
Add optional dynamic variables in key value pairs of string
that injects into your Response Engine prompt and tool
description. Only applicable for Response Engine.
This is what it should be:
retell_llm_dynamic_variables:
type: object
additionalProperties: string # string instead of {}
example:
customer_name: John Doe
description: >-
Add optional dynamic variables in key value pairs of string
that injects into your Response Engine prompt and tool
description. Only applicable for Response Engine.