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 referenceIntroduction

Introduction

Base URLs, the JSON response envelope, and how to read the API reference.

The Getme API lets you build on the platform — sites, commerce, bookings, and more. It is organized around REST, uses resource-oriented URLs, returns JSON, and relies on standard HTTP response codes and verbs.

Base URL

text
https://api.getmeonline.io

A staging environment is available at https://api-staging.getmeonline.io for testing against non-production data.

Requests

  • All requests are made over HTTPS; plain HTTP is not supported.
  • Request and response bodies are application/json.
  • Endpoints are versioned under the /v1 path prefix.

Responses

Successful responses use a consistent envelope:

json
{
  "success": true,
  "data": {}
}

The data field holds the resource — or a list of resources — that you requested. Errors use the same envelope with success set to false; see Errors.

On this page

  • Base URL
  • Requests
  • Responses