Title:
OAuth app with valid client_id returns "doesn't exist" on figma.com/oauth endpoint — private app published to team
Description:
We created a private OAuth app via figma.com/developers/apps, published it to our team (Creative AdBundance), and configured a redirect URI. However, when we try to authorize using the standard OAuth URL:
https://www.figma.com/oauth?client_id=8eKIYXCkESoJweas8kHFwX&redirect_uri=https://www.figma.com/oauth/mcp/callback&scope=file_content:read&state=n8n&response_type=codeWe get: "OAuth app with client id 8eKIYXCkESoJweas8kHFwX doesn't exist"
The client_id is confirmed correct — it matches exactly what's shown in the OAuth credentials page of our developer dashboard. The app status shows as Private, published to Creative AdBundance.
We've tried:
- Different redirect URIs (our own server + https://www.figma.com/oauth/mcp/callback)
- Different scope combinations
- Multiple browsers and incognito mode
- A second app created by the team Owner — same error
Figma support confirmed the MCP OAuth flow is only for Figma Make. We're trying to use a standard OAuth 2.0 authorization_code flow to get an access token for the Figma REST API.
Has anyone successfully gotten a private OAuth app to work with the
figma.com/oauthauthorization endpoint? Is there a step we're missing after publishing?
