pin_version, unpin_version, revert_version

Unified version management for pages, components (header/footer), html_head, theme, and snippets.

Resources serve their latest version by default. Pinning freezes a resource to a specific version — that version is what visitors see.

Actions

pin

Pin a specific version as the live version. Requires user confirmation. Not for reverting to old content — use revert_version.

Parameters:

• website — Website subdomain, domain, or UUID
• target — Resource to pin:
  • theme
  • html_head
  • header, footer
  • snippet:<path> (e.g. snippet:css/style.css)
  • a page path (e.g. /about)
  • unpinned — pin all unpinned resources to their latest version in one call (e.g. launching a new website without pinning each page separately). version_number is not used with this target.
• version_number — Version number to pin

Pinning a page freezes its snippet versions — the page keeps serving the exact snippet versions it referenced at pin time, so editing a snippet can't change what a pinned page shows.

unpin

Unpin a resource so it serves the latest version instead of a frozen one. Requires user confirmation. Not for removing old content — use delete_page/delete_snippet.

Parameters:

• website — Website subdomain, domain, or UUID
• target — Resource to unpin (theme, html_head, header, footer, snippet:<path>, or a page path)

revert

Revert a resource to a previous version by creating a new version with the old content. Does not delete any versions. Not for freezing to a specific version — use pin_version.

Parameters:

• website — Website subdomain, domain, or UUID
• target — Resource to revert (theme, html_head, header, footer, snippet:<path>, or a page path)
• version_number — Version number to revert to

OAuth Scopes