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.

Order Booster
Commerce API
    Getting StartedCatalog IntegrationOrder Status UpdatesStore Management
    API Reference
powered by Zuplo
Commerce API

Getting Started

The Commerce API allows Online Ordering Solutions, POS systems and other Commerce Platforms to act as a Menu Source and Order Destination for Gett.

Data Flow

Your system is the source of truth for catalogs, store status, and order updates. Gett is the source of truth only for order creation.

DataSource of TruthDirectionAPI
Catalog / MenuPartnerPartner → GettPOST /catalogset-notification
Store StatusPartnerPartner → GettPOST /stores/{id}/status
Order CreationGettGett → PartnerplaceOrder webhook
Order UpdatesPartnerPartner → GettPOST /orders/{id}/status

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 Placement: We call your placeOrder webhook when a customer pays.
  4. Order Updates: You send status updates as orders progress.
  5. Store Status: Pause/resume stores in real-time.

Setup Prerequisites

  1. API Key: We issue you a key to authenticate your calls.
  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
  • Order Status Updates — Sending updates
  • Store Management — Pause/resume
Commerce APICatalog Integration
On this page
  • Data Flow
  • High-Level Flow
  • Setup Prerequisites
  • Authentication
  • What's Next