Accessing Rovo Agent Conversation Histories via GraphQL or REST API

Question

Is there an API (GraphQL or REST) to programmatically retrieve Rovo Agent conversation histories from Studio (Live conversations enabled)?

We're looking to:

- Access conversation data programmatically

- Integrate with external tools/dashboards

- Archive or analyze conversation logs

What options are available?

Sami Shaik · Answer

@Francisco Castrillo ,

@Arkadiusz Wroblewski is right: there is no REST or GraphQL endpoint for agent conversations today. Two facts from the live documentation that shape what you can do in the meantime, because the second one is a deadline.

1. What Live conversations gives you, and to whom. Per Atlassian’s page Review live conversations with your Rovo agent, transcripts are visible in Studio, Conversation review, Live tab to the agent’s creators and managers only; an org admin or Studio admin sees them only if they also hold one of those agent roles. You get the full transcript, the thumbs ratings and written feedback. There is no export or download on the page and no API mentioned.

2. The retention clock is 30 days. The same page: “All conversations expire 30 days after the last message was sent in the conversation.” So “archive or analyse later” is not available even manually; anything you want to keep has to be captured within a month of the conversation ending. If you have a compliance need for these logs, raise it with Atlassian Support now, before you build anything.

3. Where the gap is tracked. Two suggestions cover your ask, and both are worth your vote and a comment describing the dashboard use case:

* ROVO-356 (conversation transcripts for Rovo agents), In Progress, 27 votes, created October 2025, last updated June 2026.
* ROVO-1034 (export the data from Rovo Studio Insights), Gathering Interest, created July 2026.

Until one of those ships, the only programmatic surface is indirect: an agent action that writes a summary of each conversation into a Jira work item or a Confluence page as part of its own flow, which you then query through the normal APIs. That captures what you design it to capture, not the transcript, so treat it as a workaround with a known gap, not a logging system.

References:

*

https://support.atlassian.com/rovo/docs/review-live-conversations-with-your-rovo-agent/

*

https://jira.atlassian.com/browse/ROVO-356

*

https://jira.atlassian.com/browse/ROVO-1034

Arkadiusz Wroblewski · Answer

Hello @Francisco Castrillo

At the moment it's not possible.

There's open an Feature request

https://jira.atlassian.com/browse/ROVO-516

Best,

Arek🤠🧙‍♂️