Hello Atlassian Community,
We have just announced the requestRemote bridge API, which allows Forge apps to integrate directly with remote backends from the UI Kit and Custom UI applications via the Forge bridge.
Our goal for the requestRemote API was to create a lightweight method for UI and Custom UI apps to interact with Forge remote backends. This specifically applies to requests tied to UI experiences, where the latency overhead of proxying from the Forge platform back to the remote was not optimal.
requestRemote is an implementation of this FRGE-1856, asking for direct UI client to remote access, but is also a workaround for several other feature requests, including:
-
Improving InvokeRemote response - https://ecosystem.atlassian.net/browse/FRGE-1402
- requestRemote will return a Fetch Response object, which contains the HTTP status code, the raw body, and headers for non-2XX status responses.
-
Allow Forge UI modules to have a hosted resolver as well as a remote endpoint - https://ecosystem.atlassian.net/browse/FRGE-1398
- requestRemote will allow you to make requests to your remote without requiring you to define the resolver as the endpoint for your remote, leaving the resolver slot free for a function.
This API is similar to invokeRemote bridge method, where requests include a Forge Invocation Token (FIT) as a bearer token in the authorization header. The main difference is that the requestRemote API does not create an invocation context that passes through the Forge platform. Therefore, requestRemote will not include OAuth tokens, even if configured for the remote, and will not be reflected in invocation metrics in the Developer Console. For more details on requestRemote, please refer to the documentation.
We hope this new API enables the adoption of the Forge platform for several currently blocked use cases, especially for those migrating from Connect to Forge.
Best regards,
Bo Yang Zhang