Flavoso APIAPI reference

API reference

Every operation of the API with its scope, parameters, fields, errors and examples, read from the OpenAPI specification.

This reference is built from the OpenAPI specification that also describes the API itself. What is here is there, and the other way round. Field descriptions are in English, as in the specification.

Base URL
https://api.flavoso.com/v1
Authentication
Every request carries Authorization: Bearer <access_token>. How to get a token is explained under Authentication; to try things out, a test token is enough.

Specification

The whole API as OpenAPI 3.1 at https://api.flavoso.com/v1/openapi.json, as a Postman collection at https://api.flavoso.com/v1/postman.json. Both without authentication.

Connection

The connection between your app and one restaurant. GET /me is the first call of every integration: which restaurant, which scopes, test or live (livemode), which plan. DELETE /connection ends the connection from your side.

Orders

Read, accept, reject, cancel and advance orders, and take them over with your own id. The lifecycle of an order is described under Order flow, taking orders into a till under POS integration.

Menu

Read the whole menu, sync it in one call with PUT /menu, report sold-out items and create, change and delete categories, products, option groups and options one by one. More under Menu sync.

Store

Opening status, opening and delivery hours, special days, lead times, order types and pausing online ordering.

Tables and areas

The restaurant's tables and areas, for example to assign a reservation to a table. Read only, with store:read or reservations:read. The key in a table's QR code is never included.

Reservations

Read reservations, look up free times, create, change and move reservations through their statuses. Pro plan and up. More under Reservations.

Reports

Sales per day, week or month and sales per dish, by the same rules as the figures in the dashboard. More under Reports.

Events

The same events that webhooks deliver, for you to fetch: for POS systems without a public address and for catching up after an outage. More under Fetching events.

OAuth

The endpoints of the sign-in: authorization in the browser, token exchange, revocation and metadata. Authorization is a page at https://app.flavoso.com/oauth/authorize, because that is where the owner signs in; token exchange, revocation and metadata live at https://api.flavoso.com, outside /v1. The flow step by step is described under Authentication.

Still unclear? Write to support@flavoso.com and include the id from X-Request-Id. It lets us find your request in the log.