Changelog

Additional support for page branches

For branched pages, you can now use the isBranch and branchId parameters for additional details. These parameters are included in the following endpoint responses:

• List pages
• Get page settings
• Update page settings
• Get page content

New APIs for retrieving comments

Webflow’s API now supports operations to retrieve comments on a site with these new endpoints:

• List all comment threads - Get all comment threads for a site.

• Get comment thread - Retrieve a specific comment thread by ID with full details.

• List comment replies - Get all replies for a specific comment thread.

  Comment replies aren’t included in the initial thread listing. To retrieve replies, first get the Comment Thread ID from the list endpoint, then use that ID with the replies endpoint.

Support for additional well-known files and CMS field types

Add and manage well-known files

Upload well-known files to sites with the following requirements:

• File size must be less than 100KB per file
• Maximum of 30 files total
• Files must have one of these extensions (or no extension):
  • .txt
  • .json
  • .noext - A special extension that removes other extensions when uploaded. This helps compatibility with tools that require file extensions
    Example: apple-app-site-association.noext.txt will be uploaded as apple-app-site-association

New CMS field type: Option

• Create Option fields
  Option fields let you define a predefined list of choices for a collection item. You can add these fields either when creating a new collection via the create collection endpoint or add them to existing collections using the create collection field endpoint.

Collection field enhancements

Create reference fields

Create reference fields in a collection using the create collection field endpoint.

To create a reference field, you’ll need to:

• Set the type property in the field object to either MultiReference or Reference
• Include the metadata property with the collectionId of the target collection

1
{
2
  "displayName": "Authors",
3
  "type": "Reference", 
4
  "metadata": {
5
    "collectionId": "580e63fc8c9a982ac9b8b745"
6
  }
7
}

You can add reference fields in two ways:

• During initial collection creation via the create collection endpoint

• To an existing collection using the create collection field endpoint

Create multiple collection fields during collection creation

Create multiple collection fields during collection creation using the create collection endpoint. Collections are limited to 60 fields per collection.

Updated publishing behavior for collection items

Starting December 2024, Webflow is introducing an improved publishing workflow for collection items. When a live item’s isDraft property is set to true, the item will continue to remain published on the live site even after a full site publish. This allows users to make updates to the collection item in a draft state without changing what’s visible on the live site.

To remove an item from the live site, you must now explicitly call the unpublish endpoint. This change gives developers more precise control over the publishing state of individual items. Please see the “publishing items” section of the CMS guide for more details.

• Create CMS Item
  The default behavior of the createItem API is now to create a draft item. All new items will be created with the isDraft flag set to true.

• Publish CMS Item
  Due to changes in how publishing is handled, sites with multiple domains are no longer required to have their domains in sync when publishing a single CMS Item. Previously, users would receive a 409 error when attempting to publish a CMS item while the domains weren’t in sync. Users will no longer receive a 409 error when attempting to publish a CMS item.

Page and component content updates

We’ve updated the request body structure for updating content:

• Update page content
  To update a nested Component Instance within a Component, use the propertyOverrides property instead of using the properties property.

• Update component content
  To update a nested Component Instance within a Component, use the propertyOverrides property instead of using the properties property.

Improved management of form submissions

List form submissions by site - A new endpoint that lets you retrieve form submissions across your entire site. Unlike the existing List Form Submissions endpoint, this endpoint:

• Takes siteId as a path parameter
• Accepts elementId as a query parameter to filter by formElementId
• Works seamlessly with forms in components, where each component instance gets a unique formId but shares the same formElementId

To use this endpoint, first get the formElementId from the List Forms API, then pass both the siteId and formElementId to retrieve all submissions for a specific form, even when it appears in multiple component instances.

Support for bulk authoring, editing, and deleting CMS items

We’ve added bulk CMS item authoring, editing, and deleting, supporting up to 100 items per request. These endpoints can help manage previous rate limit issues and makes managing large content sets more efficient.

New endpoints

• Update Collection Items
  Update a single item or multiple items in a Collection. This endpoint can update up to 100 items in a request.
• Delete Collection Items
  Delete Items from a Collection. This endpoint can delete up to 100 items in a request.
• Update Live Collection Items
  Update a single live item or multiple live items in a Collection. This endpoint can update up to 100 items in a request.
• Delete Live Collection Items
  Remove an item or multiple items from the live site. Deleting published items will un-publish the items from the live site and set them to draft. This endpoint can delete up to 100 items in a request.
• Update Localized Component Properties
  Update the properties of a component definition in a specified locale.

Updated endpoints

• Create Collection Items
  Create a single item or multiple items in a Collection. This endpoint can update up to 100 items in a request.
  Note: This endpoint was previously used to create a single Collection Item for multiple locales. The endpoint can now handle requests for multiple items in multiple locales.

Updated payloads

• Form Submission
  Added schema and formElementId properties to the Form Submission webhook payload for better form visibility

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.

• 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.

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.

Enhanced security and permissions, and new endpoints for site configuration

In this latest release, we’ve rolled out some significant updates to our APIs. First up, we’ve strengthened security by ensuring that only Workspace Admins can manage changes to Apps. In the Data API, we’ve introduced new endpoints that give you greater control over robots.txt files and site redirects. And for those using the Designer API, you can now subscribe to alerts when users select new CMS items on collection pages, making it simpler to keep track of automatically generated page paths.

Security & permissions

• Enhanced Workspace App Management Permissions:
  Previously, all members within a Workspace had the ability to manage Apps (for example, uploading new bundles, updating redirect URIs). Apps now enforce stricter permissions, allowing only Workspace Admins to perform these actions. This ensures that sensitive operations are restricted to authorized personnel.
• Mandatory 2FA for Workspace Admins:
  To further enhance security, Workspace Admins are now required to have two-factor authentication (2FA) enabled to upload new App Bundles. This additional security layer helps protect your Workspace from unauthorized access and potential threats.

New endpoints

Robots.txt

• Replace robots.txt: Replace the robots.txt configuration for various user agents.
• Update robots.txt: Update the robots.txt configuration for various user agents.
• Delete user-agent rules: Remove specific rules for a user-agent in your robots.txt file.

Site redirects

• Get site redirects: Fetch a list of all URL redirect rules configured for a specific site.
• Create a site redirect rule: Add a new URL redirection rule to a site.
• Delete site redirect rules: Remove URL redirection rules from a site.

Support for robots.txt

In this latest release, we’ve added new endpoints to the Data API giving you more tools to access site configurations, and new methods to the Designer API, allowing you to determine a user’s permissions and capabilities in the Webflow Designer.

New endpoints

• Get robots.txt: Retrieve the robots.txt configuration for various user agents.