Webflow API
/user version retirement
Deprecated, no dateSubscribe to Webflow APIShare
The /user endpoint has been deprecated without a specific shutdown date. While existing calls may continue to function for a time, the endpoint will ultimately fail once the v1 API is fully retired. This change affects any integration sending requests to /user on api.webflow.com.
Calls it hits
/user
What to use instead of these calls
Move to Data API v2 (GET /v2/token/authorized_by) with a v2 site token or a scoped OAuth app. The migration requires more than changing an endpoint, because v1 tokens do not work with v2: you must create a v2 site token or re-authorize a scoped app.
v1 tokens do not work with v2: someone must create a v2 site token or re-authorize a scoped app.
In Webflow API's words
March 31, 2025 : Deprecation date for the v1 API. While the v1 API may continue to function after this date, it will no longer receive maintenance, updates, or support.
Facts
- API
- Webflow API
api.webflow.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Webflow API's own pages
Questions
When does this change take effect?
Webflow API deprecated /user without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Webflow 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 Webflow API 3
-
No date
/collections*Version retirement Deprecated, no date -
No date
/infoVersion retirement Deprecated, no date -
No date
/sites*Version retirement 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.