Improved API token management

Since launching the v2 of Webflow’s data APIs a few months ago, we have been working to improve the workflows around generating and managing Webflow API tokens.

Here’s what’s new:

  • We’ve introduced scoped APIs and site tokens–allowing you to generate API tokens that only have access to the site data you specify.
  • You can now generate more than one API token per site–so you can manage and configure individual API tokens as needed.
  • Finally, you can now name your API tokens, making it easier to create and track API access across different tools and uses.

A note about API v1 tokens
We will be removing the ability to generate new v1 API keys starting August 15th 2024, and sunsetting access to v1 API endpoints on January 1st, 2025.

We encourage any users currently using v1 API keys to generate new v2 API tokens, and update any relevant API calls to use our new v2 suite of APIs before August 15th, 2024. This will ensure that you can generate new API tokens as needed for your integration following that date.

You can learn more about Webflow API tokens here. Or you can learn more about how to migrate to our new APIs, please review our migration guide and additional documentation here.

I stumbled across the token updates today…looks good and simple to use.