# 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](/commerce-partners#data-flow).

## 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](https://gett-tech.com) 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:

```http
Authorization: Bearer YOUR_API_KEY
```

## What's Next

- [Catalog Integration](/commerce-partners/catalog-integration) — Menu sync
- [Order Webhooks](/commerce-partners/order-webhooks) — Receiving orders
- [Store Management](/commerce-partners/store-management) — Pause/resume
- [Commerce API Reference](/api/commerce) — Endpoints, schemas, and webhook contracts