Atlas Kitchen — Adapter Guide¶
Provider Info¶
| Field | Value |
|---|---|
| Slug | atlas-kitchen |
| Auth Type | webhook_only |
| Base URL | N/A (webhook-based, Atlas pushes to Cata) |
| API Docs | TBD |
Authentication¶
Atlas Kitchen primarily uses inbound webhooks — Atlas pushes data to Cata. No outbound API calls needed for most topics.
Input fields used¶
input.webhookUrl // Cata's webhook URL that Atlas posts to
input.config // { storeCode: "ATL-001", ... }
Key Concepts¶
- Atlas pushes order status updates via webhook
- Menu/product data may be managed directly in Atlas (not synced)
storeCodemaps an Atlas location to a Cata outlet
Topic: test_connection¶
TODO — For webhook-only providers, test may verify webhook URL is reachable or check a health endpoint if available.
Topic: list_remote_outlets¶
TODO — May not be applicable if Atlas doesn't expose a location list API. Fallback to manual text entry.
Topic: sync_outlet¶
TODO
Topic: sync_products¶
TODO
Topic: order_dispatch¶
TODO
Topic: order_status_update¶
TODO — Transform Atlas webhook payload → Cata order status.