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 - Install token lifecycle safety

July 15, 2026 - Install token lifecycle safety

Install token create and rotation now follow one-active-token semantics consistently.

Install token management now consistently enforces one active token per app install and environment.

Affected surfaces

  • Developer Portal
  • Install token API
  • Docs

Changes

  • Creating a token while the install already has an active token returns 409 app_install_token_already_active instead of an internal error.
  • Rotation atomically replaces the active token. If replacement fails, the previous token remains active.
  • The portal shows create only when no active token exists; use Rotate to replace an active token.

Developer action

If your portal integration receives app_install_token_already_active, rotate the active token or revoke it before creating a new one. Raw token values remain available only in successful create and rotate responses.

On this page

  • Affected surfaces
  • Changes
  • Developer action