Everything that runs your business is accessible over a REST API. 菜单s, prices, allergens, 订单, 客户, loyalty, reporting. OAuth2 auth, webhooks for real-time events, no vendor lock-in on your data.
Your data. Your integrations. Your platform. Built for the groups and in-house tech teams who want to go further than a closed box lets them.
Pull 订单, 菜单s, 客户, live metrics, loyalty, couriers, product catalogues, location config. Feed BI tools, dashboards, reconciliations and reports.
200 GET endpoints across 32 domains.
Update prices and allergens at scale. Create and edit products, modifiers, deals, vouchers, loyalty schemes, sales channels, location settings.
393 write endpoints across 菜单, pricing, 客户, operations.
Webhooks fire on order and 菜单 events. Push a new order into a BI pipeline the moment it's placed. Sync stock out to your warehouse. Trigger a courier.
OAuth2 auth, RFC 7807 errors, trace IDs on every response.
Every request is authenticated with an OAuth2 bearer token. All IDs are GUIDs. All endpoints are scoped to your organisation — you can't accidentally touch another operator's data.
Update pricing across variants, occasions (外送, 自提, 堂食, counter) and locations in a single call.
PROTECT_BLOCK_5_ENDResponse — 202 Accepted
PROTECT_BLOCK_6_END
Add a product to your 菜单. Same endpoint for a main, a side, a dessert, or a drink — classification is via the product group.
PROTECT_BLOCK_7_ENDResponse — 202 Accepted
PROTECT_BLOCK_8_END
Declare allergens properly — Natasha's Law compliant. Every declaration is either Contains or MayContain, with an optional note.
PROTECT_BLOCK_11_END技术支持ed allergens
PROTECT_BLOCK_12_END
Pull today's sales split by channel — website, kiosk, POS, Uber Eats, Deliveroo, Just Eat. Ideal for a morning-standup dashboard or a live board display.
PROTECT_BLOCK_13_ENDResponse — 200 OK
PROTECT_BLOCK_14_END
List active 订单 in real time, or page through history. Drill into any order for lines, 支付, timings and fulfilment status.
PROTECT_BLOCK_15_ENDPage through recent 订单
PROTECT_BLOCK_16_ENDFetch one order in detail
PROTECT_BLOCK_17_END
Want to push 订单 in or manage dispatch over API? That's available too — just talk to us about the use case and we'll send the full docs.
Six deep-dives — every page carries real endpoint paths, request and response JSON, and practical patterns for the integrations our 客户 build most often.
Auth, environments, your first API call, error handling, rate limits.
产品s, modifiers, variants, prices by occasion, allergens, deals.
Live 订单, history, refunds, lines, 支付, status, webhooks.
Profiles, loyalty tier progress, marketing segments, feedback.
Sales by channel, product mix, cash reconciliation, BI exports.
Webhooks, courier bookings, payment devices, signed payloads.
Andromeda uses standard OAuth2 and OpenID Connect. Your organisation is issued a client and secret; you exchange them for a short-lived access token and include it as a Bearer header on every call. Tokens scope automatically to your organisation and to the locations your user is permitted to see — there is no way to reach another operator's data.
PROTECT_BLOCK_19_END
All errors follow RFC 7807 — predictable shape, trace ID for support, no guessing.
Our 客户 use the API to pipe live sales into Power BI and Looker, reconcile 支付 into Xero, sync stock out to their warehouse system, automate price changes across hundreds of sites, plug loyalty data into email platforms, and feed bespoke franchisee dashboards.
Papa Johns UK runs over 400 sites on Andromeda. Founded in 1998, we've been building for 餐厅 groups longer than most of our competitors have existed. The API is how chains at that scale stay in control of their own data.
Yes. Every integration starts against our test environment at test-portal-api.azurewebsites.net (writes) and test-portal-queries-api.azurewebsites.net (reads). You get a non-production organisation, test data and a separate client credential. Promotion to production is a config change, not a code change.
The Andromeda Portal API is on OpenAPI 3.1 with additive changes as the default and semantic deprecation for breaking changes. We publish the spec directly from the running services, so it's always in sync with what the API actually does.
Yes, per-organisation rate limits apply to protect platform stability. Standard limits suit every integration we've seen. Enterprise groups with unusual throughput requirements get bespoke limits — just talk to us.
Order lifecycle (received, accepted, prepared, ready, dispatched, delivered, cancelled, refunded), 菜单 sync events, and customer events. Webhooks are signed — you verify the signature on receipt so only Andromeda can deliver them.
Yes, but it's a conversation not a self-serve feature — pushing 订单 in means routing them through the POS, 厨房 and payment flow correctly. 联系我们 about the channel you want to build and we'll walk through the right way to wire it up.
Today, full Swagger is available against the test environment with your credentials. We're preparing a public developer docs site at docs.andromeda.uk — if you're working on an integration now, tell us and we'll give you access direct.
Tell us what you want to integrate with and we'll get you credentials, docs and a technical contact.
Talk to our team