where can I find the url for the API when I want to send back in a mcp the data ? where can I find | ElevenLabs | Page 1

copper obsidianBOT Jan 6, 2026, 8:12 PM

#

AI-generated Answer for lazlo_88026

Short answer: there is no documented REST endpoint at /v1/convai/conversations/{id}/messages. To “send back” data to an ElevenLabs agent (including MCP tool results or user text), you must use the Agents WebSocket, not a POST to /messages.

What to use instead

Live conversations: connect to wss://api.elevenlabs.io/v1/convai/conversation and send a User Message or Client Tool Result event over that socket. This is the documented interface for sending messages/results back to the agent. (elevenlabs.io)
MCP integrations: the “URL” you need is your own MCP server’s URL (SSE or HTTP-streamable transport) that you register with ElevenLabs. The agent will call your MCP server, and your server streams the tool result back over that same connection—there is no ElevenLabs /messages callback to POST to. See the MCP guide and MCP server APIs. (elevenlabs.io)

Where to find conversation IDs (if you need them)

You receive conversation_id in the conversation_initiation_metadata event on the WebSocket, or you can retrieve it later via the Conversations REST APIs (list and get). (elevenlabs.io)

If you prefer SDKs for text-only chat, use the conversation.send_user_message-style calls shown in the Chat Mode guide (these route over the same WebSocket under the hood). (elevenlabs.io)

In summary: replace …/conversations/null/messages with the WebSocket workflow above, and configure MCP by pointing ElevenLabs to your own MCP server URL rather than an ElevenLabs “messages” endpoint. (elevenlabs.io)

upper summit Jan 6, 2026, 8:18 PM

#

are suggesting to connect elevanlabs with my MCP ? but its my mCP sending information to my agent !!!

copper obsidianBOT Jan 6, 2026, 8:18 PM

#

AI-generated Answer for lazlo_88026

Short answer: if your MCP is the thing sending tool results/data “to the agent,” you should register your MCP Server with the ElevenLabs Agents Platform and let the platform call it—don’t POST to a conversations/…/messages URL.

Two supported ways to feed data to an ElevenLabs agent:

Connect an external MCP Server to your agent (platform-managed tools)

Add your MCP Server (HTTP/SSE transport, headers/secret as needed) in Agents Platform. The agent will invoke your MCP tools directly and ingest the tool results automatically. Docs: Model Context Protocol overview and MCP Server API (list/get/delete, update). (elevenlabs.io)

Handle “client tools” yourself over the Agent WebSocket (you host the runtime)

During a live session, the agent emits Client Tool Call events over wss://api.elevenlabs.io/v1/convai/conversation; you respond by sending a Client Tool Result message back on the same socket. This is the documented path to push results from your runtime into the agent. (elevenlabs.io)

Notes about the URL you pasted:
/v1/convai/conversations/null/messages is not a documented endpoint. To start/continue conversations, use:

WebSocket handshake (recommended for live): wss://api.elevenlabs.io/v1/convai/conversation (pass agent_id). You’ll receive a conversation_id in the initiation metadata. (elevenlabs.io)
Signed URL to start a conversation (optionally returns a conversation_id): GET /v1/convai/conversation/get-signed-url. (elevenlabs.io)
WebRTC token for real-time sessions: GET /v1/convai/conversation/token. (elevenlabs.io)
To inspect existing sessions: GET /v1/convai/conversations and GET /v1/convai/conversations/:conversation_id. (elevenlabs.io)

If your intent is “my MCP sends information to my agent,” use option 1 (platform-integrated MCP Server). If you’re running your own client runtime, use option 2 and reply with Client Tool Result over the websocket. (elevenlabs.io)

upper summit Jan 6, 2026, 8:19 PM

#

the context is for : system__call_sid not conversation_id !

#where can I find the url for the API when I want to send back in a mcp the data ? where can I find