Gett Marketfront API
API for distribution partners to integrate food ordering into their platforms.\n\nThe API is organized by domain:\n- Stores: Discovery and store detail\n- Catalog: Menu structure lookup\n- Orders: Order validation and placement\n- Cart: Optional stateless helpers for building carts\n- Checkout: Session-authenticated checkout flow (payments, profile, addresses)\n- Session: Session management for the iframe/SDK\n\nFor details on authentication, error handling, rate limits, and caching strategies, see the API Conventions guide.
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