Skip to content
GetmeDocs
Sign inCreate account

Getting started

  • Getme developer documentation

API Reference

  • Introduction
  • Authentication
  • Errors
  • Idempotent requests
  • Metadata
  • Pagination
  • Request IDs
  • Versioning
  • Webhooks
  • Event Catalog
  • SDKs and CLI

Core Resources

  • Auth
  • Events

Site Resources

  • Forms
  • Sites

Commerce Resources

  • Brands
  • Categories
  • Products
  • Services

Crm Resources

  • Customers

Other Resources

  • Media

Dev Tools

  • CLIBeta
  • Website source with the CLIBeta
  • Webhooks with the CLIBeta
  • SDKsBeta
  • Node SDKBeta
  • Python SDKBeta

Guides

  • Guides
  • Quickstart
  • Website source workflow
  • Webhook handler

Changelog

  • Changelog
  • June 10, 2026 - Developer platform docs beta
  • July 15, 2026 - Install token lifecycle safety
  • July 15, 2026 - Source-first site development
  • July 15, 2026 - Site source navigation warnings
Loading documentation...
HomeChangelogJuly 15, 2026 - Source-first site development

July 15, 2026 - Source-first site development

Create a validated standalone site draft from custom source without an existing live site or base theme.

Developers can now create a standalone website draft and development session directly from a complete custom source tree.

Affected surfaces

  • Developer API
  • CLI
  • Node SDK
  • Python SDK
  • Docs

Changes

  • Added POST /v1/sites/development-sessions with the site_drafts:write scope.
  • The request accepts a complete files archive, validates it against the existing theme/source contracts, and creates an isolated draft and session.
  • An existing live site and base-theme selection are not required.
  • Added getme sites create, Node createFromSource(), and Python create_from_source() workflows.
  • Live publication remains owner-approved; draft creation and preview do not require an initial admin-panel publication.

Developer action

For a new custom-source project, run:

bash
getme sites init --name "Custom storefront"
getme sites create --name "Custom storefront" --message "Initial source"

API clients should call POST /v1/sites/development-sessions, not POST /v1/sites and not the live-site route POST /v1/sites/{site_id}/development-sessions.

See Website source workflow and Website source with the CLI for the complete flow.

On this page

  • Affected surfaces
  • Changes
  • Developer action