taventifor developers
Taventi for developers

Ordering and booking on any website

Taventi gives restaurants online takeaway orders and table bookings, without commission. Restaurants keep their own website; you add Taventi to it. Taventi owns the business logic (prices, availability, pickup times, free tables), so your site only shows it.
01WidgetsOne script and a few HTML tags: add-to-cart buttons, a cart with checkout, table booking. Works on WordPress, Wix, Webflow or plain HTML.02JS SDKYour own interface in React, Vue or anything else, with typed calls for menus, carts, orders and bookings.03API referenceThe public HTTP API underneath both, for any language. Also as an OpenAPI document.

The restaurant's own Taventi site (restaurant.taventi.app) is built on the same SDK and API, so nothing here is second-class: a restaurant can move from its Taventi site to your custom site without losing its menu, orders or bookings.

Before you start

  1. The restaurant has a Taventi account, with its menu filled in and takeaway or reservations turned on (Settings → Locations).
  2. You know its location slug, e.g. beastie-antwerp. The restaurant finds it, with ready-made code, under Website & widgets in its dashboard.
  3. Every public endpoint works without a key. Keys with permissions for agencies come later.

How it works

Money

Every amount is an integer number of cents in euros: 1250 is €12.50. Taventi computes every price and total on the server from the restaurant's menu; prices sent by a website are never trusted. Show the totals the API returns.

Languages

Restaurant content (names, descriptions) comes in Dutch, French and English as { "nl": "…", "fr": "…", "en": "…" }; a language can be missing, so fall back to another. Orders and bookings take a locale for the guest's emails.

Times

Times are ISO 8601 with an offset (2026-12-04T19:30:00+01:00); dates are YYYY-MM-DD in the location's time zone (Europe/Brussels).

Payment

Guests pay at pickup for now: say so clearly at checkout. There is no online payment in the API yet.

Placing an order twice

Creating an order or a booking needs an Idempotency-Key header: a new random value per checkout, sent again unchanged when you retry. A retry with the same key returns the first order instead of a second one, so a double click or a lost connection never makes two orders.

Errors

Every error has the same shape, with a stable code to act on:

HTTP 409
{
  "error": {
    "code": "pickup_time_unavailable",
    "message": "That pickup time isn't available anymore. Choose another one."
  }
}
StatusMeaning
400The request doesn't match the schema; details lists each field.
404No such location, order or booking.
409It can't be done now: closed, sold out, the time was just taken…
422A cart line can't be ordered as sent (cart_invalid).
429Too many requests from this IP address: wait and retry.