Hi there,
I’m working with Forge Storage, implementing a “sync service” to information in the GraphQL API as a proof-of-concept.
Using my Forge app I receive “This request does not contain the right authorisation scopes to access this field” for agentStudio_getAgents, as an example. I can successfully retrieve the list from the GraphQL explorer.
Presumably “opting in” to the experimental (nature of) the API here wouldn’t make a difference in the call (?), so I guess I am asking will Rovo / RovoDev / Rovo Studio activities ever be made available / am I missing something?
Many thanks,
Justin
Hey @JustinTownsend,
I can’t speak to “will [those APIs] ever be made available”. I have an open internal request asking for Rovo APIs, esp for being able to make requests to agents and the implication that would require getAgents like you requested. I can confirm that you’re not missing something. Those APIs are not public; the OAuth scopes do not exist so you cannot access them.
This is a general problem in our GraphQL: you can see a lot more metadata than is actually available to you. That’s because we use GraphQL for both internal & external purposes. Despite the name, the scope called atlassian-external is blocked from outside.