Send a message in a test conversation
Send the simulated lead’s next message in a test conversation and get the agent’s answer, with the tools it called and the lead’s stage.
Before you start
- It runs on the channel you chose when you started the conversation.
- Same rules as starting a conversation: secret API key only,
workflows:writeon MCP keys, always simulated. - Send one message at a time. While a turn is running, another message to the same conversation returns
turn_in_progress. Wait for the answer, then send the next one. - If the agent refuses the turn on purpose, for example because the lead was escalated to a person or the AI is off for it, you get 409
turn_refusedwith the cause inreason, such aslead_in_support,human_takeover, orai_not_enabled. Sending the same message again gets the same answer. A real failure returnsturn_failedinstead. - Only test conversations of your account are accepted. A real lead, or a conversation from another account, returns
conversation_not_found.
What you send
What you get back
The same fields as when you start a conversation:conversation_id, channel, reply, messages, tool_calls, status, and no_reply_reason when the agent stayed silent on purpose.
Read a turn in detail
With the Nexor MCP, passconversation_id as the lead ID to list_lead_turns and get_lead_turn to see the full reasoning of a turn.
Limits
- 30 turns per minute per API key, shared with starting conversations.
- A turn that takes more than 90 seconds returns
turn_failedwith reasontimeout.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Path Parameters
The conversation_id you got when you started the conversation. Conversations started in Playground also work.
Body
What the simulated lead writes.
1 - 4000Response
The agent answered.
ID of the test conversation. It is the test lead's ID, so it also works with GET /test-conversations and GET /leads/{id}/turns.
Same value as conversation_id.
Task ID (workflow in the API) the conversation runs on.
Simulated channel the conversation runs on. The agent writes as it would on that channel; nothing is sent.
whatsapp, webchat, sms, imessage, unsupervised-whatsapp, email, instagram, messenger The agent's text for this turn, bubbles joined by a blank line. null when the agent stayed silent on purpose.
Every message the agent sent in this turn, in order, as the lead would receive them.
Tools the agent called in this turn, in order. API keys and tokens in the arguments are masked.
Key of the lead's stage in the task after this turn.
Only when the agent stayed silent on purpose, for example terminal_tool (it reacted with an emoji) or status_paused (the stage pauses the agent).