canonical: https://jentic.com/apis/poslavu.com/poslavu

# Poslavu Lavu POS API

Lavu POS API provides programmatic access to restaurant point-of-sale data including menu groups, menu categories, menu items, orders, order contents, order payments, ingredients, and ingredient usage. The API uses form-encoded POST requests authenticated with a dataname, key, and token combination, and returns data in XML format. It supports querying existing records with filtering and pagination, as well as inserting new records into POS tables.

## For AI agents

Query and insert restaurant POS data including menu items, orders, payments, and ingredient inventory across 9 data tables.

## Scope

Does not handle online ordering, customer loyalty programs, or staff scheduling - use for POS data query and insert only.

## Capabilities

- Query menu groups, categories, and items for restaurant catalog management
- Retrieve order records with optional column-based and date-range filtering
- Insert new records into POS tables for order and inventory updates
- Access payment data linked to specific orders for reconciliation
- Track ingredient usage to monitor stock levels and cost of goods

## Use cases

### Daily Sales Reporting

Query the orders and order_payments tables to generate daily sales summaries for restaurant management. The API supports date-range filtering via value_min and value_max parameters, allowing retrieval of all transactions within a specific time window. Results include order contents and payment breakdowns for accurate revenue reporting.

Example prompt: Query the orders table for all records with value_min set to 2026-06-01 and value_max set to 2026-06-15 to retrieve this period's transactions

### Menu Catalog Synchronization

Retrieve menu groups, categories, and items from the POS to synchronize with online ordering platforms or digital menu boards. The API provides the complete menu hierarchy, enabling automated updates when items or pricing change in the POS system.

Example prompt: Query the menu_items table to retrieve all current menu items and their associated pricing data

### Inventory and Cost Tracking

Access the ingredients and ingredient_usage tables to monitor stock levels, calculate cost of goods sold, and identify items that need reordering. The API returns usage records that can be correlated with orders to track per-dish ingredient consumption.

Example prompt: Query the ingredient_usage table filtered by a specific date range to calculate total ingredient consumption for the week

### AI Agent POS Data Access via Jentic

AI agents use Jentic to discover Lavu POS operations by intent, such as 'query restaurant orders' or 'get menu items'. Jentic returns the operation schema with the required dataname, key, token, and table parameters, so agents can pull POS data without managing XML response parsing or credential handling manually.

Example prompt: Search Jentic for 'query restaurant orders', load the queryData operation schema, and execute a request for orders from the current date

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/cp/reqserv` | Query records from POS data tables with filtering |
| POST | `/v2/reqserv/` | Insert new records into POS data tables |

## Key resources

- **Data Tables** — Query and insert operations across 9 tables: menu_groups, menu_categories, menu_items, tables, orders, order_contents, order_payments, ingredients, ingredient_usage

## Why Jentic

- **Setup:** Wiring the Lavu POS API by hand means assembling its dataname, key, and token credentials into every POST body and parsing the returned XML yourself. Through Jentic you install once, import the Lavu POS API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Lavu routes both query and insert operations through its request-service endpoints with the target table in the request body, so you limit the agent to the operations it needs, such as querying orders. Insert operations are included only if you add them.
- **Credential handling:** Your Lavu dataname, key, and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'query restaurant orders' or 'get menu items', and Jentic returns the matching Lavu operation with its required parameters and table options so the agent calls the right endpoint without parsing the XML documentation.

## Related APIs

- **Square API** — Full-featured POS and payments platform with JSON API and broader ecosystem
- **Stripe API** — Payment processing for online transactions outside the POS
- **Plaid API** — Financial data aggregation for bank account and transaction access

## FAQ

### What authentication does the Lavu POS API use?

The Lavu POS API uses a three-part credential system: dataname (account identifier), key (API key), and token (API token). These are passed as POST body parameters with each request. Through Jentic, all three credentials are stored encrypted in the vault and injected automatically into requests.

### Can I query orders by date range with the Lavu POS API?

Yes. The query endpoint accepts value_min and value_max parameters in date-time format, allowing you to filter records within a specific time window. Combine these with the column parameter to specify which date field to filter on, such as order creation time.

### What data tables are available in the Lavu POS API?

The API provides access to 9 tables: menu_groups, menu_categories, menu_items, tables, orders, order_contents, order_payments, ingredients, and ingredient_usage. Each table is accessed through the same query endpoint by specifying the table parameter.

### What are the rate limits for the Lavu POS API?

Rate limit details are not published in the Lavu POS API specification. The API uses a limit parameter for pagination, and responses are in XML format. Contact Lavu support for account-specific rate limit information.

### How do I query restaurant orders through the Lavu POS API with Jentic?

Install the SDK with pip install jentic, then search for 'query restaurant orders'. Jentic returns the queryData operation schema requiring dataname, key, token, and table fields. Set table to 'orders' and optionally add date filters, then execute the call to receive order records.

### What format does the Lavu POS API use for requests and responses?

Requests use application/x-www-form-urlencoded format for query operations. The insert endpoint also uses form encoding but includes an XML-formatted contents field for the record data. All responses are returned in XML format, not JSON.

### Can I limit what my agent is allowed to do with the Lavu POS API?

Yes. Because Jentic One is self-hosted, your own rules decide which Lavu operations and credentials the agent may use. The Lavu POS API routes both query and insert calls through its request-service endpoints with the target table set in the request body, so you can grant the agent only the operations it needs, such as querying the orders or menu_items tables. Insert operations are included only if you choose to add them, and your dataname, key, and token stay under your control at execution time.