Logs come from post-call webhooks, not real-time API interception
ElevenLabs logs are populated from transcription webhooks sent after a voice conversation ends — not from intercepting LLM API calls. This has significant implications for what data is available.
What the prompt and response fields contain
| Field | Contents |
|---|---|
| User Prompt | All user-side utterances from the full conversation, joined |
| Assistant Response | All agent-side utterances from the full conversation, joined |
These are transcripts of the whole call, not individual turns.
Most fields are always blank
The webhook payload does not include: model name, temperature, input/output token counts, latency, or system prompt. All of these will always be blank for ElevenLabs logs.
Structured outputs
Not applicable — ElevenLabs is a voice AI platform, not a text generation API.
Caching
Not applicable.
What ElevenLabs logs are useful for
Conversation quality review, feedback collection on voice interactions, and volume tracking. Not useful for cost analysis (no token counts) or performance benchmarking (no latency or model data).