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...
HomeAPI referenceVersioning

Versioning

The API is versioned by date; pin a version to keep your integration stable.

The Getme API is versioned by date. The current public API contract version is:

text
2026-06-09

The generated OpenAPI document uses this value as info.version, and each operation includes the same value in x-getme-api-version. Official SDKs send it in the Getme-Version request header. If you call the API directly, send the same header to pin your integration to the documented contract:

bash
curl https://api.getmeonline.io/v1/sites \
  -H "Authorization: Bearer $GETME_API_KEY" \
  -H "Getme-Version: 2026-06-09"

Backwards-incompatible changes ship under a new dated version. Additive changes, such as new fields on a response, may appear within a version without a version bump, so write your integration to ignore unrecognized fields.

When a new version is released, review the changelog before upgrading, and test against staging first.