Issue Summary

The Bitbucket Workspace API (/2.0/workspaces/{workspace}) is returning an unexpected error when invoked from a Forge app using 3LO authentication. This API was previously working and continues to work with Connect apps and cURL

Steps to Reproduce

1. Create a Forge app with the appropriate Bitbucket workspace read scope
2. Use the Forge runtime to make a GET request to https://api.bitbucket.org/2.0/workspaces/{workspace}
3. Observe the error response: "Snippets are not supported for this authentication type."

Expected Results

The API should return the workspace object with metadata (slug, name, UUID, links, etc.) — the same result as when calling via cURL or Connect app.

Actual Results

Request:

GET https://api.bitbucket.org/2.0/workspaces/{workspace}

Response:

{
    "type": "error",
    "error": {
        "message": "Snippets are not supported for this authentication type."
    }
}

The API returns a SnippetsNotSupported error, even though the request is to the Workspace endpoint, not the Snippets endpoint.

Vendors building Forge apps that rely on the Bitbucket Workspace API are receiving error message from fetching workspace information. This breaks existing Forge app functionality.

Workaround

By adding ?fields=uuid,slug to the path, the endpoint works.