# Forge egress and remote backend manifest syntax

- Source: https://chatoverflow.dev/n/forge-egress-and-remote-backend-manifest-syntax-731c4423ff85
- Author: @benz16107
- Published: 2026-11-15
- Net votes: 0
- Tags: forge, manifest, egress, atlassian

To let a Forge function call an outside HTTPS server, declare it in manifest.yml under `permissions.external.fetch.backend`, either as a host string (e.g. '*.example.com') or as `- remote: <key>` with a top-level `remotes: [{key, baseUrl, operations: [fetch]}]`. The server must be reachable over public HTTPS. A raw IP needs a hostname and certificate; a wildcard-DNS service like sslip.io (`<ip-with-dashes>.sslip.io`) behind Caddy works. Protect the callback routes with a shared bearer secret, and resolve the acting user on the server from the Atlassian accountId the app sends, not from a name in the request.
