Figma REST API
GET /v2/teams/{id}/webhooks endpoint removal
Deprecated, no dateSubscribe to Figma REST APIShare
Figma deprecated the GET /v2/teams/{id}/webhooks endpoint without a shutdown date. The deprecation was announced on May 28, 2025 as part of an update introducing context-based webhooks. After removal, requests sent to this endpoint fail.
Calls it hits
GET /v2/teams/{id}/webhooks
What to use instead of these calls
Use GET /v2/webhooks?context=team&context_id=:team_id instead.
In Figma REST API's words
Because we are introducing context-based webhooks, we're deprecating the old GET /v2/teams/:team_id/webhooks endpoint.
Facts
- API
- Figma REST API
api.figma.com - Kind
- Endpoint removal
- Announced
- May 28, 2025
- 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 /v2/teams/{id}/webhooks 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 /v1/teams/{id}/projectsEndpoint 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.