SDKs and CLI

You can call the API directly over HTTP, or use an official client:

• Node SDK — a typed client for JavaScript and TypeScript.
• Python SDK — a client for Python services and scripts.
• CLI — install, authenticate, and sync sites and themes from your terminal or CI.

Each SDK handles authentication, pagination, retries, request IDs, idempotency, and error parsing for you. The CLI uses the same public developer API model for terminal and CI workflows.

Current Node SDK resource helpers include commerce resources, forms read helpers, public media, and website source workflows. Current CLI resource commands include getme forms list|get, getme media ..., commerce reads and mutations, and site source workflows. The SDKs expose source-first development session creation, and the CLI exposes it as getme sites create, so a custom source project does not need an existing live site or selected base theme.

When to use each surface

Use the SDKs from server-side application code. They are best for integrations, scheduled jobs, backend services, and webhook handlers.

Use the CLI from a terminal or CI pipeline. It is best for authenticating, inspecting resources, syncing website source, validating files, creating previews, and opening owner-gated publish requests.

Credentials

Protected API calls use app-install access tokens such as gmat_test_... or gmat_live_.... Keep those tokens on the server or in trusted CI secrets. Do not expose them in browser code, mobile apps, logs, or client-side build output.

Website publication safety

The SDKs and CLI can save changes to development sessions and create previews. They can also create publish requests. They do not bypass owner-gated live publication.