List test conversations
List test conversations
List your most recent Playground tests with the task they ran on and their last messages, to check what the agent answered.
GET
List test conversations
When you try an agent in Playground, Nexor creates a test lead for that conversation. Test leads never show up in the lead lists, so this endpoint is the way to find them again. Use it to check what the agent answered in a test that went wrong, before you change its instructions.
It returns your most recent tests first, with the task each one ran on and its last messages.
Before you start
- MCP keys need
leads:read. Full-access REST keys need nothing else. - Only Playground tests are returned. Real leads are never included.
- It is read-only. Calling it does not send anything to anyone.
- Errors return a stable code in
error, such asinvalid_limit. Map the code to your own copy.
Choose what to read
What you get back
Read what the agent did
With the Nexor MCP, passlead_id to list_lead_turns and get_lead_turn. Each turn shows the agent’s reply, the tools it called, and any tool error. That tells you whether the problem is in the instructions, in a tool, or in something the platform does not do yet.
Limits
- At most 25 conversations per request.
- Message text is cut at 280 characters. API keys, tokens, and signatures are masked. Anything the tester typed is returned as written, so treat it as conversation data.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Query Parameters
Task ID (workflow in the API). Only tests that ran on that task. A malformed ID returns 400 invalid_workflow_id; a task from another account returns an empty list.
How many conversations to return. Any other value returns 400 invalid_limit.
Required range:
1 <= x <= 25Last modified on October 2, 2026