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 referenceRequest IDs

Request IDs

Every API response carries a request correlation id to help with debugging and support.

Every API response includes an X-Correlation-ID header. Getme treats this value as the request id for support, logs, and debugging.

If you send X-Correlation-ID or X-Request-ID, the API reuses that value. If you do not send one, the API generates a new id and returns it as X-Correlation-ID.

Log this header alongside your own records, especially for unexpected 4xx or 5xx responses. The id identifies a single HTTP request and is safe to store and share with support.

Not a resource id

Some resources also have fields or path parameters named request_id. Those are resource identifiers. For API debugging, use the X-Correlation-ID response header.