For developers

The Flavoso API

Orders, menu, opening hours, reservations and sales of a restaurant, over REST and webhooks. Connections use OAuth 2.0, with the owner's consent.

Free developer account Quickstart API reference

No restaurant of your own and no subscription needed. A test restaurant with data is included.

# The test token from the developer console (valid for up to one hour)
export ACCESS_TOKEN="flv_at_..."

curl https://api.flavoso.com/v1/me \
  -H "Authorization: Bearer $ACCESS_TOKEN"

{
  "object": "connection",
  "id": "4b3f7c1e-9a2d-4e8b-b5f6-0c1d2e3f4a5b",
  "livemode": false,
  "app": {
    "client_id": "flv_app_...",
    "name": "Example POS"
  },
  "tenant": {
    "id": "7d0e5b8a-3c41-4f2e-9a6b-1e2d3c4b5a69",
    "name": "Test restaurant",
    "slug": "test-k7q2m9",
    "timezone": "Europe/Berlin",
    "currency": "EUR",
    "country": "DE"
  },
  "scopes": [
    "orders:write",
    "menu:write",
    "store:write",
    "reports:read"
  ],
  "plan": "pro",
  "rate_limit": {
    "limit": 120,
    "window_seconds": 60
  },
  "created_at": "2026-10-04T17:40:00.000Z"
}

What you can build

An app works on behalf of a restaurant, with exactly the scopes its owner agreed to. A few examples:

POS systemsOrders land in the till and are taken over with your own receipt number. The POS maintains the menu, prices and sold-out items, and reconciles sales at night.Delivery softwareTake over delivery orders with address and requested time, report the status back, pause online ordering at rush hour.AccountingFetch sales per day, tax rate, payment method and order type, by the same rules as the figures in the dashboard.ReservationsLook up free times, book tables, confirm reservations and seat guests.AutomationReact to events: new order, status change, sold out, pause. Signed, with retries and a log.

How it works

Your app calls the REST API at https://api.flavoso.com/v1. Every request carries an access token, and every token belongs to exactly one connection between your app and one restaurant.

A connection is created when an owner agrees to your app (OAuth 2.0 with PKCE). Whatever changes in the restaurant, Flavoso reports to your server by webhook; a POS without a public address fetches the same events with GET /events.

Your app

POS, delivery, accounting, your own system

Flavoso API

REST at api.flavoso.com/v1

Restaurant

Ordering page, kitchen, dashboard, phone app

1
Connect
The owner agrees to your app (OAuth 2.0). Your app receives tokens for exactly this restaurant.
2
Request
Your app reads and writes with the token: orders, menu, hours, reservations, sales.
3
Events
Flavoso reports every change to your server by webhook, or your app fetches them with GET /events.

Five steps to your first integration

1
Create an account
A free Flavoso account is enough, without a restaurant and without a subscription.
2
Create an app and a test restaurant
In the console, the setup assistant guides you: the app's name, where it runs and its scopes, then the test restaurant with a menu, tables and tools.
Console
3
Get a test token and make requests
One click under Credentials, then GET /me and GET /orders. Done in two minutes.
4
Add OAuth and webhooks
That is how every restaurant will connect your app later, with events sent to your server.
5
Submit for review
Once approved, every restaurant can connect your app, and if you choose, it appears in the app directory.