Rovo API: Missing actions (skills) in agent details response – has the schema changed or is there a

[Harsh Raval]

Hi everyone,

I am currently working on an automation workflow that interacts with Atlassian Rovo agents via the internal gateway API. Specifically, I’ve been using the following endpoint to fetch agent configurations, including their associated actions (skills):

---

curl --location 'https://studio.atlassian.com/gateway/api/assist/rovo/v1/agents/{{agentId}}' \
--header 'x-cloudid: {{siteId}}' \
--header 'x-experience-id: ai-mate' \
--header 'x-product: rovo' \
--header 'Authorization: Basic {{authToken}}'

---

The Issue: Previously, this request returned a comprehensive payload that included the actions associated with the specific agentId. However, I’ve recently noticed that the actions array is empty in the response, even for agents that clearly have skills configured in the UI.

Why I need this: My automation relies on parsing these skills to programmatically validate agent capabilities before triggering specific tasks. Without this metadata, my integration is unable to map which tools the agent has access to.

My Questions:

1. Has there been a recent change to the v1/agents/ response schema where skills have been deprecated or moved?

2. Is there a specific header or query parameter required now to "expand" the actions or tools in the response?

3. If this data has been decoupled, is there an alternative API endpoint I should call to fetch the list of skills assigned to a specific Rovo agent?

Any guidance from the community or the Atlassian team would be greatly appreciated!

[mr john]

I’ve run into something similar recently; some endpoints require an additional expand=actions query parameter to include skills in the payload. Also, double-check if your auth token has full read permissions for agent configurations; restricted scopes can return empty arrays. Might be worth testing with GET /agents/{{agentId}}?expand=actions to see if that fixes it.

[Harsh Raval]

Hey @mr john, thank you for responding. The token has read permissions and I have tried with full scope of permissions as well. Also, tried with ?expand=actions, didn't work for me. Did it work for you?

[Harsh Raval]

@mr john Is there any specific documentation that you're referring to? It would be great if you could share. I tried with the query params and with a higher-level access token, but I'm getting the response as below:

scenarios: [{
  actions: [] 
}]