Missing apps:read scope for Retool API token (403 on GET /api/v2/apps)

[Shawn_Seffernick]

We’re trying to call: GET /api/v2/apps
Using an org access token created via Settings → Retool API → Create new. The API returns
{
"success": false,
"message": "Forbidden: API token is missing one of "apps:read" or one of "mcp:admin""
}
However, in the token creation UI, the only scopes available to select are:
Retool RPC
Custom Component Libraries (Read / Write)
We do not see Apps → Read (apps:read) or mcp:admin as options.
Docs say tokens are created in Settings → Retool API and that “Not all scopes may yet be available for your organization”:

Configure Retool API authentication | Retool Docs

Questions:
How do we enable/receive the apps:read scope so /api/v2/apps works? Is this a feature flag / plan / org setting?
If the UI can’t show it yet, is there an official way to mint a token with apps:read (e.g. via an access token creation endpoint with scopes: ["apps:read"])?
Goal: list apps via /api/v2/apps with a properly scoped access token.

[Darren]

Hey @Shawn_Seffernick - welcome to the community! Apologies for letting this question slip through the cracks. Unfortunately, many of the documented API endpoints are currently scoped to Enterprise plans, with a subset also made available to Business plans. You can see the breakdown here.

That said, most of the same functionality - including the /apps endpoint - is exposed via our MCP for all plan levels! Would that meet your needs?