1 Quality scores, point by point
The API returns every quality score on a conversation, with its scorecard, its reviewer and the result of each point. Each conversation in a list carries its average score and how many scores it has, and lists filter by manual or automatic scoring.
2 The topics of each conversation
The API returns the topics found in each conversation, from your own topic catalog, so your reports can count them by account, agent or team. One request turns topic, agent and team IDs into names.
3 Summaries in your own format
The API returns each summary with its text and the name of the prompt that wrote it. Summary prompts in Gen AI Studio write plain text or structured JSON, so a summary can hold the fields your reports need; the plan comparison shows which plans include your own prompts.
4 The IDs that join it to your data
Each conversation carries its ID, start time, length, direction, type, agent and team, and the data that came with it from other systems, often a call ID your phone system also writes into a CRM or help-desk ticket. Which IDs arrive depends on how conversations reach Ender Turing. Your system can add its own data to a conversation through the API.
5 Pulled on your schedule
Your ETL job, a script or an AI agent lists conversations with any filter of the Conversations screen, one day or one week at a time. An exact count for the same filter, with the conversations' total length, shows whether the filter works and how many conversations each load should hold.
6 Pushed as each result is added
An Ender, one of Ender Turing's automation rules, calls your webhook when a conversation is added, when the system it came from updates it, or when a score or a summary is added. Its JSON body holds the conversation's details, agent and team, with the summaries, topics and scorecard scores it has by then, and a mapping of your own can reshape it.