Integrations & API

What it is

This page is the honest map of the boundary. Everything a venue runs on — orders, kitchen, bookings, menu, inventory, rosters, marketing, compliance, the website — is built into NexDine. The integrations hub exists for the things that are external by nature: your payment processor, your accountant's software, your existing mailbox, delivery marketplaces, and tools you already use and aren't ready to leave.

What problem it solves

Hospitality software loves two kinds of dishonesty: pretending it does everything, and quietly being a thin shell over ten other subscriptions. NexDine's position is plainer — the restaurant-management tooling is genuinely built in, the external connections are genuinely optional, and every one of them is set up, health-checked and managed from inside NexDine.

How it works

1. The integrations hub lists every available connection as a card with its live status. Connecting is either an authorisation with the provider (Stripe, Xero, Google Workspace, Microsoft 365, Google Business Profile) or an API key entry (Deliverect, Doshii, SevenRooms, Epos Now) — and saving credentials always requires a fresh identity check.

2. Deeper integrations get their own pages: Stripe Terminal for card-present payments, Lightspeed K-Series two-way POS sync, Deputy rostering with shift swaps, Tanda / Workforce.com, Meta and WhatsApp messaging, Cloudbeds and Mews lodging PMS, and Microsoft 365 calendar sync. Xero's operational sync — daily journals and invoices — lives with your finance pages.

3. Health checks run against every connection on demand, showing last success, last failure and what went wrong — so a silently expired token is a dashboard row, not a mystery. A webhook events feed shows recent inbound traffic from the POS, rostering and lodging connections.

4. The developers page is your own integration surface: create scoped API keys — shown once, stored hashed, rate-limited — for reading and writing orders and bookings and reading customers and inventory through a versioned API. Changes made through the API run the same rules as the venue's own screens.

5. Subscribe your own endpoints to outbound webhooks — orders created, bookings created and updated, payments captured, low stock — each delivery HMAC-signed and retried with backoff, with a delivery log for debugging.

Everything inside the system

• Integrations hub with connection status, health checks, plan-aware availability and step-up protected credentials.
• Connections for the inherently external: payments and card terminals (Stripe), accounting (Xero), mailboxes (Gmail, Microsoft 365), reviews (Google Business Profile), delivery and ordering channels (Deliverect, Doshii), POS (Lightspeed K-Series, Epos Now), rostering (Deputy, Tanda), reservations (SevenRooms), lodging PMS (Cloudbeds, Mews), messaging (Meta, WhatsApp), and calendar (Microsoft 365).
• Inbound webhook events feed for POS, rostering and lodging traffic.
• Public API with scoped, rate-limited keys and cursor pagination for orders, bookings, customers and inventory.
• Outbound webhooks with HMAC signatures, retries and a delivery log.

Every connection above is optional — a venue can run entirely on what's built in, with Stripe processing payments. None of them is a hidden dependency: if you don't use Xero or Deputy or a delivery marketplace, there is simply nothing to connect.