What NomNom connects to

Your booking system should not be an island. Here is every way NomNom talks to the rest of your setup — your till, your website, your card payments — with an honest status against each one, including the ones that are not finished.

Live use it today Partial some of it ships, some does not Coming built or building, not yet usable

Integrations

REST API

Live

Read and write bookings from your own software. Built for EPOS and till vendors who need the diary inside their own product.

  • Versioned at /api/v1, with a deliberately frozen wire format
  • API-key authentication, one key per venue
  • Cursor pagination for large date ranges
  • Free to the restaurant — no per-call or per-cover charge

Read the API reference →

Outbound webhooks

Live

NomNom pushes to you. Give us a URL and every booking change arrives as JSON, so you are not polling an API for something that may never have changed.

  • Fires on created, updated and cancelled
  • Full booking in the payload: guest, party, table, deposit, notes
  • Custom headers, so your endpoint can authenticate us
  • A test button in the app, with the real status code back

Settings → Advanced → Webhooks

Stripe

Live

Card payments through your own Stripe account. The money goes to you directly — we are never in the middle of it.

  • Deposits and no-show protection on bookings
  • Gift vouchers, sold online or over the counter
  • Apple Pay and Google Pay at the checkout
  • Your bank details, your payouts, your Stripe dashboard

See what NomNom costs →

Your own website

Live

Put the booking form on your site rather than sending guests away to ours. It renders into your page — not in a frame, not in a pop-up.

  • One container and one script tag, pasted together
  • Works on WordPress, Squarespace, Wix, Shopify and Webflow
  • Inherits your page, so it reads as part of your site
  • Or link out to a hosted booking page, if you would rather

Setup guides in the Knowledge Base →

Mailchimp

Partial

Connect your Mailchimp account and choose the audience that diner marketing opt-ins belong to.

  • Connect with an API key, from Settings → Email & SMS
  • Pick which of your audiences to use
  • Guests who opt in when booking online are recorded with consent
Not finished: the automatic sync is not built yet, so opt-ins are recorded in NomNom but are not pushed to Mailchimp on their own. Connecting today means you are set up for when it lands.

Reserve with Google

Coming

A “Reserve a table” button on your Google listing, going straight into your diary. NomNom is an approved Google booking partner and the integration is built.

  • Your real availability, under your own booking rules
  • Bookings land allocated a table, like any other
  • No commission, on any cover it sends you
Not live yet: we are working through Google’s own review and approval process, and no restaurant is taking public bookings this way today. We will say so here the day that changes.

What we do not connect to

Worth knowing before you switch, rather than after. None of these exist today, and we would rather you heard it here than found out in month two. If one of them is the thing that decides it for you, tell us — what customers actually ask for is how this list gets shorter.

  • EPOS and till systems We have no named till partner with an off-the-shelf connection. The REST API above is the route, and your vendor does the work.
  • Accounting software No Xero or QuickBooks integration. Booking and payment data comes out as reports and through the API.
  • Delivery and takeaway platforms Nothing for Deliveroo, Uber Eats or Just Eat. NomNom covers tables, not delivery orders.
  • Zapier and no-code tools No Zapier app. The webhooks above are the closest thing, and they need somewhere to point.

Building on NomNom?

If you sell software to restaurants and you need the reservation book inside it, the API is documented, versioned and free to the venue. The contract is frozen on purpose: we will add fields, but we will not quietly change what you already read.

curl https://api.nomnom-app.net/api/v1/reservations \ -H "X-Api-Key: your-key-here"
Read the API reference Talk to us about an integration

Common questions

Does NomNom have an API?

Yes. NomNom has a public REST API at /api/v1 for reading and writing reservations, authenticated with an API key issued per venue. It is documented in the developer reference and is free to the restaurant — there is no per-call or per-cover charge for using it.

Can NomNom send booking data to another system automatically?

Yes, using outbound webhooks. You register a URL in Settings under Advanced, and NomNom sends it a JSON packet whenever a booking is created, changed or cancelled. You can attach custom headers so your endpoint can authenticate the request, and send a test request to check the wiring before you rely on it.

Does NomNom integrate with my EPOS or till system?

There is no off-the-shelf connection to a named till system today. What exists is the public REST API and outbound webhooks, which is the route an EPOS vendor would use to build one. If your till supplier wants to integrate, point them at the developer reference — the API is free for them to use against your venue.

Can I put NomNom booking on my own website?

Yes. NomNom gives you a container and a script tag to paste into your page, and the booking form renders directly into your site rather than in an iframe or a pop-up. There are setup guides for WordPress, Squarespace, Wix, Shopify and Webflow in the Knowledge Base. If you would rather not embed anything, you can link out to a hosted booking page instead.

Does NomNom charge commission on bookings?

No. NomNom charges a flat monthly subscription per venue and takes nothing per cover or per booking, through any of the channels on this page. Card payments go through your own Stripe account, so deposits and voucher sales are paid directly to you.