AI-generated Answer for kumanday_intelligence
Short answer: Today you cannot enable “overrideable fields” for an agent via the public API. Overrides must be explicitly enabled per field in the agent’s Security settings in the Dashboard; if you send an override for a field that isn’t enabled, the platform returns “Override is not allowed for this AI agent,” which matches the error you’re seeing. This is the documented behavior. (elevenlabs.io)
What you can do programmatically instead
- Use Dynamic Variables for personalization (first name, account data, etc.) without needing to enable overrides. Add placeholders like {{first_name}} to your system prompt or first message, then pass values in conversation_initiation_client_data.dynamic_variables when you start the conversation. This is the recommended approach for greeting users and injecting real-time context. (elevenlabs.io)
When you truly need to replace content per conversation
- Full replacements (e.g., swapping the entire system prompt, first_message, language, or voice) still require that you manually enable those specific override switches in the agent’s Security tab before sending conversation_config_override in your API/SDK call. There is no documented endpoint to toggle those switches. (elevenlabs.io)
Related docs and references
- Overrides guide (explains the need to enable per-field overrides in Security). (elevenlabs.io)
- Help Center: common failure reasons, including “Override is not allowed for this AI agent.” (help.elevenlabs.io)
- Dynamic Variables guide (how to template prompts/messages and pass values at runtime). (elevenlabs.io)
- Chat mode guide reiterating that runtime overrides require enabling the corresponding Security toggles. (elevenlabs.io)
- Twilio outbound guide also instructs enabling First message/System prompt overrides in Security before injecting them dynamically. (elevenlabs.io)
If/when an API to manage Security/override permissions is published, it will appear in the Agents Platform API reference
dark brook
wicked gobletBOT