Gett Marketfront Partner API
Gett Marketfront Partner API
API for distribution partners to discover Gett stores, read their catalogs, help build carts, and place orders.
What you can do
- Discover stores — search and browse orderable stores (
/stores/discover,/stores/{storeId}). - Read catalogs — fetch a store's menu as a normalized CatalogSet (
/catalog-sets/{catalogSetId}). - Build carts (optional) — stateless helpers that compute cart totals (
/carts/*); you may implement your own cart logic instead. - Validate & place orders — preview pricing then place with a saved card (
/orders/validate,/orders/place).
Payment
Orders are paid with CARD_ON_FILE — a card token from your own payment solution, passed in paymentToken. Gett works with your existing payment solution: the secure interchange is configured with your Gett representative during onboarding, so you keep using the payment infrastructure you already have.
Authentication
Include your API key in every request via the Authorization header using the Bearer scheme:
Code
Tags
Stores
Store discovery and detail. Use discoverStores to find stores available at a location (with optional free-text query and fulfillment filtering), and getStore to fetch a single store's full payload — including address, availability windows, categories, and the
catalogSetId for the follow-up Catalog call.Catalog
Menu structure lookup. getCatalogSet returns the complete CatalogSet for a store using a normalized dictionary structure (id-to-object maps) for O(1) lookups and zero duplication.
CatalogSets are immutable — once created, they never change. When a restaurant updates their menu, a new CatalogSet is created with a new ID. Cache aggressively using
catalogSetId as the cache key. Conditional requests via If-None-Match are supported.Orders
Order validation and placement.
- validateOrder — Validate the cart, get accurate pricing, and receive a
validatedOrderToken - placeOrder — Submit the order using the token (expires in 15 minutes); requires the
Idempotency-Keyheader (UUID v4)
Cart
Optional stateless convenience endpoints that simplify common cart operations. These are pure functions —
(existingCart, operation) → newCart — with no server-side state.
Why use them?
- Accurate pricing using current CatalogSet prices
- Modifier validation (required selections, limits)
- Consistent cart structure ready for order validation