Lavu website screenshot

Lavu

Lavu is a cloud-based iPad restaurant point-of-sale system, now positioned as an AI-powered restaurant intelligence platform, serving restaurants, bars, and hospitality businesses with POS, payments, inventory, and reporting. Lavu promotes an open API that lets developers and restaurants extend the point of sale, build peripheral components, and create tailored integrations without waiting on vendor roadmaps. The POSLavu API is a POST-based interface where a single request server accepts form-encoded credentials (dataname, key, token) plus a table selector and returns XML rows; documented tables include menu_groups, menu_categories, menu_items, tables, orders, order_contents, order_payments, ingredients, and ingredient_usage. Records can be written with cmd=insert and an XML contents payload. Credentials are retrieved from the API tab of the POSLavu Control Panel, and the developer documentation is published at admin.poslavu.com; API access comes with an active Lavu account.

1 APIs 0 Features
RestaurantPoint of SalePaymentsInventoryMenu Management

APIs

Lavu (POSLavu) API

A POST-based data API for the Lavu restaurant POS. A single request server accepts form-encoded dataname, key, token, and table parameters and returns XML rows; reads support co...

Collections

Pricing Plans

Lavu Plans Pricing

4 plans

PLANS

Rate Limits

Lavu Rate Limits

1 limits

RATE LIMITS

FinOps

Lavu Finops

FINOPS

Semantic Vocabularies

Lavu Poslavu Api Context

7 classes · 161 properties

JSON-LD

API Governance Rules

Lavu API Rules

31 rules · 4 errors 18 warnings 9 info

SPECTRAL

JSON Structure

Poslavu Api Menu Category Structure

16 properties

JSON STRUCTURE

Poslavu Api Menu Group Structure

4 properties

JSON STRUCTURE

Poslavu Api Menu Item Structure

32 properties

JSON STRUCTURE

Poslavu Api Order Content Structure

41 properties

JSON STRUCTURE

Poslavu Api Order Payment Structure

47 properties

JSON STRUCTURE

Poslavu Api Order Structure

58 properties

JSON STRUCTURE

Poslavu Api Table Structure

8 properties

JSON STRUCTURE

Example Payloads

Poslavu Api Menu Item Example

32 fields

EXAMPLE

Poslavu Api Order Example

58 fields

EXAMPLE

Poslavu Api Table Example

8 fields

EXAMPLE

Resources

🔗
Website
Website
📰
Blog
Blog
💰
Pricing
Pricing
🔗
LinkedIn
LinkedIn
🔗
Plans
Plans
🔗
RateLimits
RateLimits
🔗
FinOps
FinOps
🔗
Rules
Rules
🔗
Vocabulary
Vocabulary
🔗
JSONLD
JSONLD

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: Lavu (POSLavu) API
  version: '1.0'
items:
- info:
    name: Menu
    type: folder
  items:
  - info:
      name: Lavu Query a POSLavu Table
      type: http
    http:
      method: POST
      url: https://admin.poslavu.com/cp/reqserv/
      body:
        type: form-urlencoded
        data: []
      auth:
        type: apikey
        key: token
        value: '{{token}}'
        placement: query
    docs: Retrieve rows from a POSLavu data table. Provide the `dataname`, `key`, and `token` credentials from the API tab
      of the POSLavu Control Panel, select the `table`, and optionally filter with `column`/`value` (exact match) or `column`/`value_min`/`value_max`
      (range), and paginate with `limit` (offset,count). Responses are returned as XML `<row>` elements.
- info:
    name: Orders
    type: folder
  items:
  - info:
      name: Lavu Insert Records Into a POSLavu Table
      type: http
    http:
      method: POST
      url: https://admin.poslavu.com/cp/reqserv/insert
      body:
        type: form-urlencoded
        data: []
      auth:
        type: apikey
        key: token
        value: '{{token}}'
        placement: query
    docs: Insert one or more records into a POSLavu data table. Send `cmd=insert`, the target `table`, and a `contents` field
      containing one or more XML `<row>` payloads. Writes target the v2 request server (https://admin.poslavu.com/v2/reqserv).
      On success for an order insert, the API returns a `<result>` element containing the new `<id>` and `<order_id>`. Note
      this path is documented via the `cmd=insert` POST variable rather than a distinct URL path; it is modeled here as a
      separate operation for clarit
bundled: true