Skip to navigation

Data Export API: proactive_ids on the Conversations endpoint

The v2 Conversations endpoint of the Data Export API now returns proactive_ids on each conversation. The list holds the Proactive ID of each Proactive that opened the conversation, in the order they first opened it.

The list is empty when no Proactive opened the conversation. A Proactive can open a conversation that already exists, so the list can have more than one ID.

Use the field to count the conversations that each Proactive opened. Count a conversation under every Proactive in its list.

A later Proactive opening updates date_updated, so updated_since exports return the conversation with the new ID.

See the Conversation object reference for the full schema.


Simulations: see what your External systems text leaves out

A simulated run now tells you when your test case left out a value that an API tool set to Mock returns. Before, the AI Agent acted on an empty value, and the run looked like an AI Agent fault.

Simulation analysis lists What External systems leaves out below your text:

  • An output that came back empty, when your text names neither the output nor its API tool.
  • A record written as JSON that has no key that an output of the API tool reads.

Each item says what to add to the External systems text.

Who this affects

Every test case that uses an API tool set to Mock. The list is available for 24 hours after the run.

See Mock API tools.