Changelog

Bulk discard changes

You can now discard multiple unpublished changes at once. Select the changes you want to discard the same way you select changes to publish.

To learn more, see Discarding changes.

Create pages and update regions in bulk from the REST API

Two new endpoints create many pages or update many regions at a time, and Create Regions moves to the same $bulk path.

POST /v6/pages/$bulk

PATCH /v1/regions/$bulk

• Same response shape: like Create Regions, both return one result per item, in request order: { "success": true, "data": ... } or { "success": false, "error": { "code": ..., "message": ... } }. An error in one item doesn’t keep the others from being written.
• Create Regions moved: POST /v1/regions/batch is now POST /v1/regions/$bulk. The old path no longer exists.

For details, see Create Pages and Update Regions.

List pages with their element trees from the REST API

The List Pages endpoint now accepts include=elements, returning each page’s element tree alongside the page records.

GET /v6/pages?siteId={siteId}&include=elements

• Opt-in: omit include and every page’s elements is null. include accepts only elements (any other value returns a 400).

For details, see the include parameter on List Pages.

Create regions in batches from the REST API

A new v1 endpoint creates many regions in one request.

POST /v1/regions/batch

[
  { "success": true, "data": { "object": "region", "id": "header", "version": 1, ... } },
  { "success": false, "error": { "code": "REGION_EXISTS", "message": "..." } }
]

• Error codes: a failed region reports REGION_EXISTS, BASE_REGION_MISSING, INVALID_LOCALE, INVALID_ELEMENT_TREE, DUPLICATE_IN_BATCH, or INTERNAL_ERROR. Only INTERNAL_ERROR is worth retrying.
• Default locale first: regions in the default locale are created before regions in site locales, so a region in a site locale may come before its default locale’s region in the same batch.

For details, see Create Regions.

Update and delete regions from the REST API

Two new v1 endpoints complete the region API: you can now replace a region’s element tree and delete a region.

PATCH /v1/regions/{id}?siteId={siteId}

DELETE /v1/regions/{id}?siteId={siteId}

• Region versions: every region response now includes version, which increases with every change to the region’s element tree.
• Safe updates: pass the version from an earlier read to Update Region. If the region changed since, the request returns 409 and changes nothing. Leave version out to update the region regardless.

For details, see Update Region and Delete Region.

Delete typographies from the REST API

A new v4 endpoint lets you delete a site’s typography.

DELETE /v4/typographies/{id}

The delete is unconditional: Text elements that still reference the typography aren’t checked, so update them first if they should keep a style.

For details, see Delete Typography.

Manage regions from the REST API

Three new v1 endpoints let you create, list, and read a site’s regions, including their element trees, from the REST API.

GET /v1/regions?siteId={siteId}

POST /v1/regions

GET /v1/regions/{id}?siteId={siteId}

• You choose the ID: Makeswift doesn’t generate region IDs. You assign the ID (for example, site-header), and it must be unique within a site and locale.
• One locale per request: all three endpoints accept a locale parameter, as either a locale code like en-US or a site locale UUID. If you leave it out, the request uses the site’s default locale. A region has to exist in the default locale before you can create it in another locale.
• Element trees are optional: pass include=elements to List Regions or Get Region to get each region’s element tree. Without it, elements is null.

For details, see List Regions, Create Region, and Get Region.

Runtime v0.29.0

@makeswift/runtime v0.29.0 fetches snapshots faster and rebuilds how Makeswift generates CSS and applies style updates. It also has breaking changes that may require updates to your host.

• React 19 required. Your host must run React 19. Next.js hosts must be on Next.js 15 or later.
• cacheKey renamed to classNamePrefix. The cacheKey prop on <RootStyleRegistry> is now classNamePrefix (default ms). Use it to set a custom prefix for Makeswift-generated CSS class names.
• <RootStyleRegistry> required for Pages Router. Pages Router hosts must now wrap their content in <RootStyleRegistry> inside ReactRuntimeProvider:

<ReactRuntimeProvider runtime={runtime} siteVersion={siteVersion}>
  <RootStyleRegistry>
    <Component {...pageProps} />
  </RootStyleRegistry>
</ReactRuntimeProvider>

• New forceImportant prop. Set forceImportant on <RootStyleRegistry> to add !important to Makeswift-generated CSS declarations, so they win when your site’s own CSS conflicts with them.

For migration steps, see the v0.29.0 upgrade guide. For component details, see the <RootStyleRegistry> reference.

Manage site typographies from the REST API

Four new v4 endpoints let you create, read, and update a site’s typographies (the text styles in the Visual Builder) from the REST API.

GET /v4/typographies?siteId={siteId}

POST /v4/typographies

GET /v4/typographies/{id}

PATCH /v4/typographies/{id}

• Per-device styles: style is an array of { deviceId, value } entries. Each value can set fontFamily, fontSize ({ value, unit }), fontWeight, lineHeight, letterSpacing, textAlign, italic, underline, strikethrough, uppercase, and color.
• Colors come from swatches: color.swatchId takes the id of an existing swatch, so create the swatch first with the Swatch API. color.alpha (0–1) sets opacity.
• Two IDs: the typography endpoints use id. referenceId is the value a Text element’s typography prop uses in a page’s element tree, so use it to find a typography in page content.

For details, see List Typographies, Create Typography, Get Typography, and Update Typography.

Makeswift Embed is now HTML Embed

The Makeswift Embed component has been renamed HTML Embed to better describe what it does and to make it quicker to find when you want to add your own HTML. Functionality is unchanged.