Integration

Loyverse integration

Loyverse is a point of sale (POS) system for shops, cafes and restaurants. An agent can read and record sales receipts and refunds, read and adjust inventory levels per store, and manage items, variants, categories, modifiers, discounts, taxes, customers, suppliers, POS devices and webhooks, and read stores, employees, shifts, payment types and merchant details. Item image upload is not exposed. Authentication is a personal access token from the Loyverse Back Office (Settings, Access tokens) sent as a Bearer token; it gives full access to the account. The limit is 300 requests per 300 seconds per account.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Loyverse.Built from the 56 Loyverse tools below, on the connection you add once.

What you can do with Loyverse

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Category, 4 operations

  • create_or_update_categoryCreate or update categoryPOSTCreates an item category, or updates one when id is given. Sending id overwrites that existing category with the values given.
  • delete_categoryDelete categoryDELETEDeletes an item category by id. Returns deleted_object_ids.
  • get_categoryGet categoryGETGets one item category (name, color) by its id, as returned by list_categories.
  • list_categoriesList categoriesGETLists item categories, newest first, optionally only the ids given in categories_ids. Pass the returned cursor to get the next page.

Customer, 4 operations

  • create_or_update_customerCreate or update customerPOSTCreates a customer, or updates one when id is given (name required; email, phone, address, customer_code, note, points balance, which it overwrites). Sending id overwrites that existing customer with the values given.
  • delete_customerDelete customerDELETEDeletes a customer by id. Loyverse then erases the customer data permanently, usually 24 hours later (the permanent_deletion_at time). Returns deleted_object_ids.
  • get_customerGet customerGETGets one customer by id: contact details, customer_code, note, loyalty points balance, first and last visit and total spent.
  • list_customersList customersGETLists customers (with loyalty points balance and visit totals), newest first; filter by customer_ids, email, or created/updated date range. Pass the returned cursor to get the next page.

Discount, 4 operations

  • create_or_update_discountCreate or update discountPOSTCreates a discount, or updates one when id is given. type sets which value applies: discount_percent for FIXED_PERCENT, discount_amount for FIXED_AMOUNT. Sending id overwrites that existing discount with the values given.
  • delete_discountDelete discountDELETEDeletes a discount by id; it can then only be seen with show_deleted on list_discounts. Returns deleted_object_ids.
  • get_discountGet discountGETGets one discount by id: type, amount or percent, stores where it applies and whether it needs a password on the POS.
  • list_discountsList discountsGETLists discounts (type, amount or percent, stores), newest first; filter by discount_ids or created/updated date range.

Item, 4 operations

  • create_or_update_itemCreate or update itemPOSTCreates an item with its variants, or updates one when id is given. Pass variants with prices per store; returns the item with variant ids. Sending id overwrites that existing item and its variants with the values given.
  • delete_itemDelete itemDELETEDeletes an item by id; deleted items appear only with show_deleted on list_items. Returns deleted_object_ids.
  • get_itemGet itemGETGets one item by id with its variants, category, taxes, modifiers, composite components and per-store prices.
  • list_itemsList itemsGETLists items with their variants, prices per store, category, taxes and modifiers, newest first; filter by items_ids or created/updated date range. Pass the returned cursor to get the next page.

Modifier, 4 operations

  • create_or_update_modifierCreate or update modifierPOSTCreates a modifier with its options (name, price), or updates one when id is given. Sending id overwrites that existing modifier and its options with the values given.
  • delete_modifierDelete modifierDELETEDeletes a modifier by id. Returns deleted_object_ids.
  • get_modifierGet modifierGETGets one modifier by id with its options and option prices.
  • list_modifiersList modifiersGETLists modifiers with their options and prices, newest first; filter by modifier_ids or created/updated date range. Pass the returned cursor to get the next page.

Pos device, 4 operations

  • create_or_update_pos_deviceCreate or update pos devicePOSTCreates a POS device (register) in a store, or renames one when id is given. Sending id overwrites that existing POS device with the values given.
  • delete_pos_deviceDelete pos deviceDELETEDeletes a POS device (register) by id. Returns deleted_object_ids.
  • get_pos_deviceGet pos deviceGETGets one POS device (register) by id: name, store and whether it is activated.
  • list_pos_devicesList pos devicesGETLists POS devices (registers), optionally only those of one store (store_id).

Receipt, 4 operations

  • create_receiptCreate receiptPOSTRecords a real sale with its payment: it counts in sales reports and, with customer_id, earns that customer loyalty points. store_id is required; pass line items, discounts, taxes and one payment.
  • get_receiptGet receiptGETGets one receipt by receipt number: type (SALE or REFUND), totals, line items, discounts, taxes, payments, customer and points.
  • list_receiptsList receiptsGETLists sales and refund receipts with line items, discounts, taxes and payments, newest first; filter by store_id, receipt_numbers, order, source, or created/updated date range. Pass the returned cursor to get the next page.
  • refund_receiptRefund receiptPOSTRecords a money refund against a sales receipt, deducts the loyalty points the sale earned and restocks the refunded items. Only single-payment receipts; integrated POS payments are refused.

Supplier, 4 operations

  • create_or_update_supplierCreate or update supplierPOSTCreates a supplier, or updates one when id is given (name required; contact, email, phone, website, address, note). Sending id overwrites that existing supplier with the values given.
  • delete_supplierDelete supplierDELETEDeletes a supplier by id. Returns deleted_object_ids.
  • get_supplierGet supplierGETGets one supplier by id: company, contact person, email, phone, website and address.
  • list_suppliersList suppliersGETLists suppliers (company, contact, address), newest first, optionally only suppliers_ids. Pass the returned cursor to get the next page.

Tax, 4 operations

  • create_or_update_taxCreate or update taxPOSTCreates a tax (name, rate, INCLUDED or ADDED type, stores), or updates one when id is given. Sending id overwrites that existing tax with the values given.
  • delete_taxDelete taxDELETEDeletes a tax by id. Returns deleted_object_ids.
  • get_taxGet taxGETGets one tax by id: name, rate, INCLUDED or ADDED type and stores.
  • list_taxesList taxesGETLists taxes (rate, INCLUDED or ADDED type, stores), newest first; filter by tax_ids or created/updated date range.

Variant, 4 operations

  • create_or_update_variantCreate or update variantPOSTCreates a variant on an existing item (item_id), or updates one when variant_id is given: sku, barcode, option values, cost and price. Sending variant_id overwrites that existing variant with the values given.
  • delete_variantDelete variantDELETEDeletes one item variant by id. Returns deleted_object_ids.
  • get_variantGet variantGETGets one item variant by id: sku, barcode, option values, cost, default price and per-store price and availability.
  • list_variantsList variantsGETLists item variants (sku, barcode, option values, cost, price and availability per store); filter by variants_ids, items_ids, sku or date range. Pass the returned cursor to get the next page.

Webhook, 4 operations

  • create_or_update_webhookCreate or update webhookPOSTCreates a webhook for one event type sent as POST to an https url, or updates one when id is given. Each type and url pair must be unique. Sending id overwrites that existing webhook with the values given.
  • delete_webhookDelete webhookDELETEDeletes a webhook by id. Returns deleted_object_ids.
  • get_webhookGet webhookGETGets one webhook by id: target url, event type and status.
  • list_webhooksList webhooksGETLists webhooks: Loyverse returns only the webhooks created by the application making the request.

Employee, 2 operations

  • get_employeeGet employeeGETGets one employee by id: name, email, phone, stores and whether they are the account owner (is_owner).
  • list_employeesList employeesGETLists employees (name, email, phone, role, stores), newest first; filter by employee_ids or created/updated date range. Pass the returned cursor to get the next page.

Inventory level, 2 operations

  • list_inventory_levelsList inventory levelsGETLists current stock levels (in_stock) per item variant and store; filter by store_ids, variant_ids or updated date range. Pass the returned cursor to get the next page.
  • update_inventory_levelsUpdate inventory levelsPOSTOverwrites the stock of item variants per store: each entry gives variant_id, store_id and stock_after, the new absolute stock (not a delta), which replaces the current level. Returns the updated levels.

Payment type, 2 operations

  • get_payment_typeGet payment typeGETGets one payment type by id: name, type (CASH, NONINTEGRATEDCARD, CHECK, OTHER or an integrated provider such as SUMUP) and stores.
  • list_payment_typesList payment typesGETLists payment types (cash, card, other) configured in the account; filter by payment_type_ids or created/updated date range.

Shift, 2 operations

  • get_shiftGet shiftGETGets one closed shift by id: store, POS device, opening and closing times and cash amounts, payments and taxes.
  • list_shiftsList shiftsGETLists closed cash register shifts (opening and closing cash, sales and payment totals), newest first; filter by store_ids or created date range. Pass the returned cursor to get the next page.

Store, 2 operations

  • get_storeGet storeGETGets one store by id: name, address, phone and description.
  • list_storesList storesGETLists the stores of the account (name, address, phone); filter by store_ids or created/updated date range.

Item image, 1 operation

  • delete_item_imageDelete item imageDELETERemoves the image of an item by item id.

Merchant, 1 operation

  • get_merchantGet merchantGETGets the merchant account: business name, email, country and currency (code and decimal places).

Use Loyverse from Claude Code, Cursor or Codex

Connect Loyverse in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Loyverse operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Loyverse

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Loyverse once

    Add your Loyverse connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Loyverse integration FAQ

What can you do with the Loyverse integration?

LiveContext exposes 56 operations on Loyverse, covering category, customer, discount and item.

Popular integrations

Browse the whole catalog