Gett Developer Portal
  • Welcome
  • Distribution Partners
  • Brand Partners
  • Commerce Partners
  • Ecosystem Partners
  • Errors
  • API Reference
Documentation
  • Get Started
  • Marketfront SDK
  • API Reference
Resources
  • Payments
Company
  • Gett
  • Terms of Service
  • Privacy Policy

Copyright 2026 Gett. All rights reserved.

Getting StartedCatalog IntegrationOrder WebhooksStore Management
API Reference
powered by Zuplo
Commerce Partners

Getting Started

The Commerce API lets Online Ordering Solutions, POS systems, and other commerce platforms act as a Menu Source and Order Destination for Gett. Your system stays the source of truth for catalogs; Gett is the source of truth for order creation — see the data-flow overview.

High-Level Flow

  1. Catalog Notification: Notify us when a menu changes for a store.
  2. Catalog Pull: We download the CatalogSet from your URL.
  3. Order Validation: We call your validateOrder webhook before the customer pays to confirm pricing and availability.
  4. Order Placement: We call your placeOrder webhook after successful payment.

Setup Prerequisites

  1. API Key: Gett provisions your partner account and issues your first key during onboarding — it is not self-serve. Contact Partner Support to get started, then manage and rotate keys in the Developer Portal.
  2. Webhook Base URL: Where you host your order endpoints.

Authentication

Include your API key in all requests via the Authorization header using the Bearer scheme:

Code
Authorization: Bearer YOUR_API_KEY

What's Next

  • Catalog Integration — Menu sync
  • Order Webhooks — Receiving orders
  • Store Management — Pause/resume
  • Commerce API Reference — Endpoints, schemas, and webhook contracts
Catalog Integration
On this page
  • High-Level Flow
  • Setup Prerequisites
  • Authentication
  • What's Next