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.

Lavu publishes 4 APIs on the APIs.io network, including Inventory API, Menu API, Orders API, and 1 more. Tagged areas include Restaurant, Point of Sale, Payments, Inventory, and Menu Management.

The Lavu catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Lavu’s developer surface includes authentication, engineering blog, pricing, and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

40.8/100 thin ▼ -7.5 Agent 37/100 agent ready Full breakdown ↓
scored 2026-07-28 · rubric v0.6

AccessPaidSelf serve

4 APIs

RestaurantPoint of SalePaymentsInventoryMenu Management

Kin Score

Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6

Composite quality — 40.8/100 · thin

Contract Quality 14.2 / 25

Developer Ergonomics 2.6 / 20

Commercial Clarity 10.0 / 20

Operational Transparency 2.7 / 13

Governance 8.3 / 12

Discoverability 5.6 / 10

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/lavu: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Rate Limits 1

Documented rate limits and quota policies.

Lavu Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

JSON Schema 7

Standalone JSON Schema definitions for this provider's data models.

Scroll for all 7

Examples 7

Example request and response payloads for these APIs.

Scroll for all 7

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Rules

Rules

Vocabulary

Vocabulary

JSONLD

JSONLD

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

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
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/lavu.png
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:lavu-inventory-api
  name: Lavu Inventory API
  description: Ingredients and ingredient usage.
  tags:
  - Inventory
  properties:
  - type: OpenAPI
    url: openapi/lavu-inventory-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
- aid: lavu:lavu-menu-api
  name: Lavu Menu API
  description: Menu groups, categories, and items.
  tags:
  - Menu
  properties:
  - type: OpenAPI
    url: openapi/lavu-menu-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
- aid: lavu:lavu-orders-api
  name: Lavu Orders API
  description: Orders, order contents, and payments.
  tags:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/lavu-orders-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
- aid: lavu:lavu-tables-api
  name: Lavu Tables API
  description: Restaurant floor table layout.
  tags:
  - Tables
  properties:
  - type: OpenAPI
    url: openapi/lavu-tables-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
common:
- type: AgenticAccess
  url: agentic-access/lavu-agentic-access.yml
- type: DomainSecurity
  url: security/lavu-domain-security.yml
- type: Authentication
  url: authentication/lavu-authentication.yml
- 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: kin@apievangelist.com

Lavu

APIs 4

Open Collections 1

Pricing Plans 1

Rate Limits 1

FinOps 1

Semantic Vocabularies 1

Spectral Rules 2