Figma REST API
POST /v1/oauth/refresh endpoint removal
Deprecated, no dateSubscribe to Figma REST APIShare
The POST /v1/oauth/refresh endpoint was deprecated on May 16, 2025, without a shutdown date. It continues to be supported for now, but calls to it will eventually fail once removed. This change affects callers of the POST /v1/oauth/refresh endpoint.
Calls it hits
POST /v1/oauth/refresh
What to use instead of these calls
Refresh tokens using POST /v1/oauth/token with grant_type=refresh_token.
In Figma REST API's words
The legacy endpoint will continue to be supported for now, but we recommend you migrate to using the new endpoint.
Facts
- API
- Figma REST API
api.figma.com - Kind
- Endpoint removal
- Announced
- May 16, 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 POST /v1/oauth/refresh 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
GET /v2/teams/{id}/webhooksEndpoint 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.