Changes for internal APIs affecting site data sync in the browser
To support real-time collaboration, we’re implementing version control on a set of internal APIs used to read and write site data to the designer from the browser. To ensure continued functionality of browser extensions and tools that currently use this set of APIs, please see the timeline and migration steps below.
Please note: If you’re building apps with Webflow’s official set of Public APIs, this won’t affect your work.
Affected internal endpoints
Starting August 13, 2025, the following internal site data sync endpoints will now support and enforce version control.
- GET
/sites/{siteName}/dom
- POST
/pages/{pageId}/dom
- POST
/sites/{siteName}/variables
- PATCH
/sites/{siteName}/variables/{variableId}
- POST
/sites/{siteName}/styles
Starting September 15, 2025, these endpoints will require a version number in all write requests. Requests without a version number will return an error.
These endpoints will be fully deprecated and removed in January 2026. We recommend updating your tools now to comply with version checks, while also planning your migration away from these endpoints before the deprecation date.
Timeline
August 13, 2025
This set of internal APIs will start returning and accepting version fields for reads and writes
August 19, 2025
DevRel hosted office hours for additional developer support. Sign up for office hours here.
Office hours & support
We understand that this is a change for some developers, and we’re here to help. Sign up for our office hours on August 19, 2025 to answer questions and help with the migration.
Additionally, you can reach out to our developer support team at developers@webflow.com for help.
Version management
Reading site data
The GET /sites/{siteName}/dom
endpoint now returns version fields for the following resources:
Versioning for interactions is not yet available
Currently, version fields aren’t returned for interactions. However, this could change in the future.
Writing site data
The following endpoints require version numbers in the request body for all writes:
- POST
/pages/{pageId}/dom
- POST
/sites/{siteName}/variables
- PATCH
/sites/{siteName}/variables/{variableId}
- POST
/sites/{siteName}/styles
Errors and responses
POST and PATCH requests to the above endpoints will return errors if the version numbers are missing or don’t match.
- 409 Conflict: Version mismatch.
A later version of the data is available. Fetch the latest data and retry the operation. - 400 Bad Request: Missing version numbers in write requests.
The request body must include a version number for each resource in the request.
Migration steps
Migrate to the Designer API before the deprecation date
Most of the functionality served by these endpoints is also available in the Designer API. We recommend migrating to the Designer API for future development for reliability and consistency. If you need additional functionality that’s not available in the Designer API, please reach out to our developer support team at developers@webflow.com to tell us what you need.
Important reminders
- This API will be fully deprecated and removed in January 2026
- Consider migrating to official Webflow APIs when available.
- Test thoroughly in development environments before deploying
Support
For questions about this migration, contact our developer support team. However, we can’t provide ongoing support for private API usage.