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 APIs0 Features
RestaurantPoint of SalePaymentsInventoryMenu Management
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...
aid: lavu
name: Lavu
description: >-
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.
type: Index
image: https://kinlane-productions.s3.amazonaws.com/apis-json/apis-json-logo.jpg
tags:
- Restaurant
- Point of Sale
- Payments
- Inventory
- Menu Management
url: https://raw.githubusercontent.com/api-evangelist/lavu/refs/heads/main/apis.yml
created: '2026-06-02'
modified: '2026-06-02'
specificationVersion: '0.19'
apis:
- aid: lavu:rest-api
name: Lavu (POSLavu) API
description: >-
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 column/value exact-match filters,
value_min/value_max range filters, and limit (offset,count) pagination, while cmd=insert writes XML row payloads.
Documented tables include menu_groups, menu_categories, menu_items, tables, orders, order_contents,
order_payments, ingredients, and ingredient_usage. Credentials come from the API tab of the POSLavu Control Panel.
tags:
- Point of Sale
- Orders
- Menu
- Inventory
properties:
- type: Documentation
url: https://admin.poslavu.com/cp/areas/api_doc.html
- type: Documentation
url: https://lavu.com/integrations/
- type: OpenAPI
url: openapi/lavu-poslavu-api.yml
common:
- type: Website
url: https://lavu.com
- type: Blog
url: https://lavu.com/blog/
- type: Pricing
url: https://lavu.com/pricing/
- type: LinkedIn
url: https://www.linkedin.com/company/lavu-inc
- type: Plans
url: plans/lavu-plans-pricing.yml
- type: RateLimits
url: rate-limits/lavu-rate-limits.yml
- type: FinOps
url: finops/lavu-finops.yml
- type: Rules
url: rules/lavu-spectral-rules.yml
- type: Vocabulary
url: vocabulary/lavu-vocabulary.yaml
- type: JSONLD
url: json-ld/lavu-poslavu-api-context.jsonld
x-common:
features:
- name: Open API
description: POST-based table query and insert API for extending the POS and building peripheral components and integrations.
- name: Menu Management
description: Read menu groups, categories, and items, and insert new menu items.
- name: Order Management
description: Read orders, line items, and payments, and insert new orders, order contents, and payments.
- name: Floor Layout
description: Read the restaurant floor table layout (coordinates, shapes, names).
- name: Inventory
description: Read ingredients and ingredient usage data.
- name: Payment Processing
description: Integrated card payment processing with dual-pricing / cash-discount options to offset card fees.
useCases:
- name: Sales Reporting and Reconciliation
description: >-
Pull orders, order_contents, and order_payments to reconcile sales and payment volume against the POS and
accounting systems.
- name: Custom Online Ordering
description: >-
Read menu structure and insert orders to power a custom or third-party online ordering experience on top of
Lavu.
- name: Inventory and Recipe Costing
description: Read ingredients and ingredient_usage to feed inventory tracking and recipe-costing tools.
- name: Peripheral Integrations
description: >-
Build tailored integrations and peripheral components against the open POSLavu API without waiting on vendor
roadmaps.
integrations:
- name: QuickBooks
description: Accounting integration.
- name: Xero
description: Accounting integration.
- name: Restaurant365
description: Restaurant accounting and operations integration.
- name: DoorDash
description: Online ordering and delivery integration.
- name: Grubhub
description: Online ordering and delivery integration.
- name: Uber Eats
description: Online ordering and delivery integration.
- name: Otter
description: Online ordering aggregation integration.
- name: Chowly
description: Online ordering aggregation integration.
- name: OpenTable
description: Reservations and loyalty integration.
- name: Marketman
description: Inventory management integration.
maintainers:
- FN: Kin Lane
email: [email protected]