Figma REST API
GET /v1/teams/{id}/projects endpoint removal
Deprecated, no dateSubscribe to Figma REST APIShare
Figma REST API deprecated the GET /v1/teams/{id}/projects endpoint without a shutdown date. The endpoint is slated for removal, and requests sent to it will eventually fail. The change was announced on August 10, 2026, marking the endpoint deprecated in favor of the folders endpoints.
Calls it hits
GET /v1/teams/{id}/projects
What to use instead of these calls
Use GET /v2/teams/:team_id/folders instead.
In Figma REST API's words
The GET /v1/teams/:team_id/projects, GET /v1/projects/:project_id/files, and GET /v1/projects/:project_id/meta endpoints are now deprecated in favor of the folders endpoints.
Facts
- API
- Figma REST API
api.figma.com - Kind
- Endpoint removal
- Announced
- August 10, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Figma REST API's own pages
Questions
When does this change take effect?
Figma REST API deprecated GET /v1/teams/{id}/projects without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Figma REST API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Figma REST API 4
-
No date
GET /v1/projects/{id}/filesEndpoint removal Deprecated, no date -
No date
GET /v1/projects/{id}/metaEndpoint removal Deprecated, no date -
No date
GET /v2/teams/{id}/webhooksEndpoint removal Deprecated, no date -
No date
POST /v1/oauth/refreshEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.