For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Resources
Get started
    • Overview
  • APIs and SDKs
    • Data API
    • Designer API
    • Browser API
  • Developer tools
    • MCP Server
    • Webflow Apps
    • Webflow CLI
    • DevLink
    • Webflow Cloud
    • Flowkit CSS Framework
    • Changelog
LogoLogo
Resources
Get started

Changelog

This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.

September 17, 2024
September 17, 2024
September 17, 2024
September 17, 2024

Subscribe to mode changes in the Designer

Designer Extensions now remain active across various modes in the Designer, including preview mode, across different locales, and on branched pages. Different capabilities are available depending on the mode, so it’s important to know when a mode changes. This update introduces a new event subscription method to help you track mode changes in the Designer.

  • Subscribe to mode changes in the Designer
    Receive real-time notifications when users switch between different Designer modes. Since each mode offers distinct capabilities based on user permissions, this subscription helps your app adapt its functionality accordingly. For detailed information about available modes and their capabilities, refer to the App Modes documentation.
Was this page helpful?
Previous

Enhanced security and permissions, and new endpoints for site configuration

Next
Built with

Improved page content APIs and support for site configuration

We’ve made a number of updates to the Data API to help you better manage components and site configurations, alongside improvements to page content handling. These changes include new endpoints for retrieving components and their properties, as well as additional functionality for .well-known files and URL redirects.

New Endpoints

Page Content & Components

Components are powerful, reusable blocks used to create consistent layouts across your site. Learn more about components in the Webflow University lesson.

New scope for components endpoints
These endpoints will require the components:read scope.
  • Get all components for a site Retrieve all components for a site. This makes it easier to programmatically access reusable design elements.
  • Get static content for a component Retrieve static content for a specific component. Note that dynamic content set via props isn’t included—use the Get Component Properties endpoint for that.
  • Get component properties Retrieve detailed information about component-specific properties for a more dynamic and customizable component experience.

Well Known Files

Webflow supports the management of .well-known files, which are commonly used for site verification and configuration with external services. At this time, Webflow only accepts the following .well-known files:

  • apple-app-site-association Used for iOS Universal Links, allowing apps to handle specific web URLs.
  • apple-developer-merchantid-domain-association Used to verify your domain for Apple Pay on the web.
  • Create Well Known File Upload or update a .well-known file to a site.
  • Delete Well Known File Remove a .well-known file from a site when it’s no longer needed.

Site Redirects

  • Update Site Redirect Update an existing URL redirection rule for a site.

Form Submissions

  • Delete Form Submission Remove an individual form submission.

Deleting form submissions will also delete the file submissions and make the submitted file URLs inaccessible. Before you delete your form submission data, back up any file uploads you want to keep.


Updated Endpoints

  • Get Page Content Now returns component instances present on a page. Note: Component instances are included only when their default property values have been modified. Additionally, only the modified properties are returned, while the component’s static content remains excluded.
  • Update Page Content Update properties on component instances directly. Use the Get Page Content endpoint to identify component IDs, and the Get Component Properties endpoint to retrieve the relevant component properties. When updating a component instance, include a list of component properties with their IDs and values. This update supports plain text, rich text, and component instances.