REST API 403 Error on v1/teams/:id/projects due to conflicting scope validation rules

Hello Team,

 

I am encountering a persistent 403 Forbidden error when trying to fetch the projects list for my team using a Personal Access Token via the REST API.

The endpoint I am targeting is:
GET https://figma.com

The Error Payload Received:

json

{
    "status": 403,
    "err": "Invalid scope(s): current_user:read, file_comments:read, file_comments:write, file_content:read, file_metadata:read, file_versions:read, library_assets:read, library_content:read, team_library_content:read, file_dev_resources:read, file_dev_resources:write, folders:read. This endpoint requires the projects:read scope"
}

Use code with caution.

Context & Technical Blockers:

1. Scope Availability: The error message explicitly states that the endpoint requires the projects:read scope. However, when generating or managing my Personal Access Token (PAT) settings in the Figma account dashboard, the projects:read scope is not visible or available to select as a granular permission option.
2. Conflicting Documentation: My token has been successfully configured with the modern granular scopes, including folders:read and file_metadata:read. However, the v1 endpoint refuses to accept these permissions, creating a catch-22 scenario where the endpoint demands a scope that cannot be assigned to a standard PAT.

Steps Taken to Troubleshoot:

• Verified the Team ID matches my workspace exactly.
• Confirmed the request is routed securely over HTTPS (://figma.com).
• Attuned the token permissions to include all necessary granular read parameters.

Could you please clarify how a standard Personal Access Token can programmatically fetch the team's project listing under this current scope mapping structure, or if there is an alternative approach for our pipeline?