Skip to content

API changes

The first version supports website-scoped credentials, managed inner-page creation and updates, manually managed/imported articles, retained image uploads, FAQ and medical schema fields, revision history, preview jobs and production publication after the website’s initial launch.

Saves preserve omitted fields. Expected revisions reject stale updates. Operation identities support safe preview/publication retries. Homepage, shared navigation, forms, design and business identity remain factory-managed.

The documentation covers Website Publishing v1, HQ MCP connections and personal HQ API tokens. The /v1 prefix identifies the Website Publishing API version.

When a contract changes, its endpoint guide and this page are updated together. Your integration should inspect HTTP errors and current MCP tool schemas rather than assuming that every account has the same enabled operations.