Forge Custom UI: Rovo Assist gateway returns 401 in app, but Rovo works in Home — how to enable prog

[Cristian Muntean]

Hi all,

I’m working on a Forge app that attempts to access Rovo programmatically via a Jira panel. My goal is for Rovo to automatically retrieve certain information from a Jira issue and provide possible solutions based on the information it has obtained from the issue.

As a user, I can open the Rovo chat in the browser (home.atlassian.com with cloudId) and talk to Rovo successfully.

From a Forge Custom UI issue panel (calling via @Forge/bridge requestJira asUser), calls to Rovo gateway endpoints return ERROR 401:

• GET /gateway/api/assist/rovo/v1/agents → ERROR 401
• POST /gateway/api/assist/rovo/v1/chat/conversation → ERROR 401 (when attempted)

In the logs I also get "Rovo proxy search failed: Authentication Required".

The app has minimal scopes (read/write Jira, read Confluence) and no external egress.

I have a few questions:

Is programmatic access to Rovo gateway endpoints supported for Forge apps at the moment (Custom UI or UI Kit)?

Are there specific settings or permissions required to allow asUser() requests from a Forge app to these endpoints?

Are there additional scopes or manifest settings needed for this to be possible?

If this API isn’t supported for apps, is there an endorsed approach to deep link into Rovo with a prefilled prompt containing informations from a Jira issue?

Thanks in advance for any help!

[Jorge Cammarota]

Specific Configurations or Permissions for asUser() Requests

Currently, there are no documented configurations or permissions that allow a Forge app to access Rovo endpoints via asUser(). The Forge permission model is restricted to standard Atlassian products (Jira, Confluence, etc.) and public APIs. Because Rovo is an assistant service, it does not expose public APIs for third-party programmatic integration via Forge.
Additional Scopes or Manifest Configurations

There are no additional scopes or manifest settings available to enable access to Rovo endpoints. Even if you include all available Forge scopes, access to Rovo remains restricted:

The Forge manifest does not include permissions for private Rovo APIs.

Access to Rovo is managed via the authenticated user interface, not through a public API.

Recommended Approach for Deep Linking with Pre-filled Prompts

If the API is not supported for apps, the endorsed approach is to use deep links to open Rovo in the user's browser (where they are already authenticated) and, when supported, pass a pre-filled prompt.

URL Structure: Rovo can be accessed via URL, for example: https://home.atlassian.com/assist/rovo?cloudId=<cloudId>

Prompt Parameters: Currently, there is no official documentation regarding parameters for pre-filling prompts, but Atlassian is rapidly evolving these integrations. It is recommended to monitor official Rovo and Atlassian product documentation for updates on deep linking capabilities.

Alternative: You can create a button or link within your Forge panel that redirects the user to Rovo. You might suggest they paste the Jira issue information (e.g., by copying it to the clipboard automatically or displaying a prompt for the user to copy).

Practical Recommendations

Deep Link: Implement a button or link in your Forge app that opens Rovo in the user's browser and guide the user to paste the ticket information.

API Monitoring: Stay tuned to the official Rovo and Forge documentation for updates regarding public APIs or programmatic integrations.

Feedback to Atlassian: Consider opening a ticket or a suggestion in the Atlassian Community to explain your use case. This can help accelerate the prioritization of a public Rovo API.