Loyverse is a point-of-sale (POS) system designed for small businesses, offering features like sales management, inventory tracking, and customer engagement tools.
Loyverse is a point-of-sale (POS) system designed for small businesses, offering features like sales management, inventory tracking, and customer engagement tools. On Nagent, Loyverse is exposed as a fully-configurable ecommerce integration that any agent can call — 58 actions, and API key authentication. No code is required to wire Loyverse into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Loyverse to automate the kinds of tasks ecommerce teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Loyverse into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Loyverse, with input parameters and output schema. Drop these into any step of an agent built in Helix.
LOYVERSE_CREATE_OR_UPDATE_CATEGORYTool to create a new category or update an existing one. If the ID field is provided, the category will be updated; otherwise, a new category is created.
Input parameters
The category ID. If provided, this will update the existing category instead of creating a new one.
The name of the category (required).
Available category colors in Loyverse
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_CUSTOMERTool to create a new customer or update an existing one in Loyverse. Use when you need to add customer records or modify customer information. If the 'id' field is provided, it will update the existing customer; otherwise, it creates a new customer.
Input parameters
Customer ID for update operation. If provided, the action will update the existing customer with this ID instead of creating a new one.
Customer's city.
Customer's full name (required). This is the primary identifier for the customer.
Additional notes or comments about the customer.
Customer's email address. Used for receipts and communication.
Customer's region, state, or province.
Customer's street address.
Customer's postal or ZIP code.
Customer's country code in ISO 3166-1 alpha-2 format (two-letter code).
Customer's phone number. Include country code for international numbers (e.g., +1234567890).
Unique customer code or loyalty card number for identification.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_DISCOUNTTool to create or update a single discount. Use when creating new discounts or modifying existing ones. Supports FIXED_PERCENT (percentage-based), FIXED_AMOUNT (fixed amount), and VARIABLE discount types.
Input parameters
The discount name.
Discount type. FIXED_PERCENT for percentage-based discounts, FIXED_AMOUNT for fixed amount discounts, or VARIABLE for variable discounts.
Array of store IDs where discount is applicable. If not provided, discount applies to all stores.
Fixed discount amount (required for FIXED_AMOUNT type). Value should be a positive number.
Discount percentage (required for FIXED_PERCENT type). Value should be between 0 and 100.
Whether discount has restricted access (requires password verification to apply).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_ITEMTool to create a new item or update an existing one in Loyverse inventory. Include the item ID to update an existing item, or omit it to create a new one.
Input parameters
UUID of the item. Include this to update an existing item, omit to create a new one.
Visual form/shape of the item (e.g., 'SQUARE', 'CIRCLE').
Display color for the item in the POS (e.g., 'GREY', 'RED', 'PINK', 'ORANGE', 'GREEN', 'BLUE', 'PURPLE').
Human-readable handle/slug for the item.
List of tax UUIDs applied to this item.
List of variants for this item with pricing and SKU info.
URL of the item's product image.
Display name of the item. This field is required.
List of component items if this is a composite item.
UUID of the category this item belongs to.
Whether inventory tracking is enabled for this item.
Whether this is a composite/bundle item.
Name of the first variant option (e.g., 'Size').
Name of the second variant option (e.g., 'Color').
Name of the third variant option.
External reference ID for integration purposes.
List of modifier UUIDs available for this item.
Whether the item is sold by weight.
Whether production workflow is enabled.
UUID of the primary supplier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_MODIFIERTool to create or update a single modifier with options. If an ID is included in the request, it will update the existing modifier; otherwise, it creates a new one.
Input parameters
Modifier ID for updates. If provided, updates the existing modifier; if omitted, creates a new modifier.
Name of the modifier
Array of store IDs where this modifier is available
Display position of the modifier in the list
Array of modifier option objects. Each option requires at least a name; price defaults to 0.00 if not provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_POS_DEVICETool to create a new POS device or update an existing one. If the request includes an ID, it updates the device; otherwise, it creates a new one.
Input parameters
Optional POS device ID (UUID). If provided, this will update an existing device instead of creating a new one.
Name of the POS device
The unique ID (UUID) of the store this POS device is connected to. Use list stores action to get store IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_SUPPLIERTool to create a new supplier or update an existing one in Loyverse. Use when you need to register suppliers before purchases or modify supplier information. If the 'id' field is provided, it will update the existing supplier; otherwise, it creates a new supplier.
Input parameters
Supplier ID for update operation. If provided, the action will update the existing supplier with this ID instead of creating a new one. Use UUID format.
Supplier city, town, or village (max 64 characters).
Name of the supplier company (1-64 characters, required). This is the primary identifier for the supplier.
Additional notes about the supplier.
Supplier email address (1-100 characters).
Supplier region (state or province). Additional address component.
Contact person at the supplier (1-64 characters).
Supplier website URL.
Supplier address line 1 (max 192 characters).
Supplier address line 2 (max 192 characters).
Supplier postal code.
Supplier country code (ISO 3166-1 alpha-2).
Supplier phone number (max 15 characters). Include country code for international numbers.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_TAXTool to create or update a single tax. If the ID field is provided, the tax will be updated; otherwise, a new tax is created. Use when setting up tax rates for stores.
Input parameters
Tax ID for updates. If provided, updates the existing tax instead of creating a new one.
Business-facing label for the tax.
The tax percentage rate (e.g., 5.545 for 5.545%, 10 for 10%).
Determines how the tax is applied. ADDED means tax is added on top of the price, INCLUDED means tax is already included in the price.
Array of store IDs where this tax applies. If not provided, tax applies to all stores.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_VARIANTTool to create or update a single item variant in Loyverse. Use when you need to add product variations (like size, color) or modify existing variant details. If variant_id is provided, it updates the existing variant; otherwise, it creates a new one. Note: The parent item must have option names defined before variants can be created.
Input parameters
Stock Keeping Unit identifier for the variant. Used for inventory tracking.
Cost price of the variant for profit margin calculations.
Array of store-specific settings including pricing, availability, and stock levels for each store where this variant is sold.
Barcode for the variant, used for scanning at point of sale.
The ID of the item this variant belongs to. The item must have option names defined (option1_name, option2_name, or option3_name) before variants can be created.
The ID of the variant to update. If provided, updates existing variant instead of creating new one. Also referred to as 'id' in some API responses.
Default selling price for the variant. Used unless overridden by store-specific pricing.
Value for the first option (e.g., 'Small', 'Medium', 'Large'). Required if the parent item has option1_name defined.
Value for the second option (e.g., 'Red', 'Blue'). Required if the parent item has option2_name defined.
Value for the third option. Required if the parent item has option3_name defined.
Purchase cost of the variant from suppliers.
Pricing type for a variant.
External reference ID for the variant, useful for third-party integrations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_OR_UPDATE_WEBHOOKTool to create a new webhook subscription or update an existing one in Loyverse. Use when you need to subscribe to events like items.update, inventory.update, receipts.create, customers.update, or shifts.create. If the 'id' field is provided, it will update the existing webhook; otherwise, it creates a new webhook.
Input parameters
The webhook ID. If provided, this will update the existing webhook instead of creating a new one.
URI where the webhook should send the POST request when the event occurs (required).
The event type to subscribe to (required). Available types: inventory_levels.update, items.update, customers.update, receipts.update, shifts.create.
The webhook status (required). Set to ENABLED to activate the webhook or DISABLED to deactivate it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_RECEIPTTool to create a sales receipt with line items and payments. Use when you need to record a sale transaction in Loyverse.
Input parameters
Additional notes for the receipt
Order reference number or name
Source application name
Array of payment methods and amounts for the receipt
UUID of the store where receipt is created
Array of line items to include in the receipt
UUID of the customer associated with the receipt
UUID of the employee processing the transaction
ISO 8601 date-time format for when the receipt was created. Defaults to current time if not specified
Array of discount objects to apply at the receipt level
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_CREATE_REFUNDTool to create a refund receipt for a sales receipt. Use when you need to process a refund for items from a previous sale. Only supports refunds for receipts paid by a single payment method (not integrated payments).
Input parameters
Source application or system creating this refund
Store ID where the refund is processed. If not provided, uses the original receipt's store.
List of line items to refund (at least one item required)
Employee ID processing the refund. If not provided, uses the original receipt's employee.
Date and time for the refund receipt in ISO 8601 format. Defaults to current time if not provided.
The sales receipt number to create a refund for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_CATEGORYTool to delete a single category by ID. Use when you need to remove an unused or deprecated category.
Input parameters
The unique ID of the category to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_CUSTOMERTool to delete a single customer by their ID. Use after confirming the customer ID to remove an existing customer.
Input parameters
The unique ID of the customer to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_DISCOUNTTool to delete a single discount by ID. Use after confirming the discount ID to remove an existing discount.
Input parameters
The unique ID of the discount to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_ITEMTool to delete a single item by ID. Use when you need to remove an item from the inventory.
Input parameters
The unique ID of the item to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_ITEM_IMAGETool to delete a single image from an item. Use when you need to remove the image associated with a specific item.
Input parameters
The unique ID of the item from which to delete the image.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_MODIFIERTool to delete a single modifier by its ID. Use when you need to remove an existing modifier.
Input parameters
The unique identifier of the modifier to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_POS_DEVICETool to delete a single POS device by its ID. Use when you need to remove a POS device from the system.
Input parameters
The unique ID of the POS device to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_SUPPLIERTool to delete a specific supplier by ID. Use after confirming the supplier ID to remove an existing supplier.
Input parameters
The unique ID of the supplier to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_TAXTool to delete a single tax by its ID. Use when you need to remove an existing tax configuration.
Input parameters
The unique identifier of the tax to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_VARIANTTool to delete a single item variant by its ID. Use after confirming the variant ID to remove an existing variant.
Input parameters
The unique ID of the variant to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_DELETE_WEBHOOKTool to delete a single webhook by its ID. Use when you need to remove a webhook configuration.
Input parameters
The unique ID of the webhook to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_CATEGORYTool to get a single category by ID. Use when you need to fetch details of an existing category in Loyverse.
Input parameters
The unique ID of the category to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_CUSTOMERTool to get a single customer by their ID. Use when you need to fetch details of a specific customer.
Input parameters
The unique UUID of the customer to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_DISCOUNTTool to get a single discount by ID. Use after confirming the discount ID to retrieve its details.
Input parameters
UUID of the discount to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_EMPLOYEETool to get a single employee by ID. Use after confirming the employee ID to fetch its details.
Input parameters
The unique UUID of the employee to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_ITEMTool to get a single item by ID including all its variants. Use when you need detailed information about a specific item from the Loyverse inventory.
Input parameters
The unique UUID of the item to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_JWKSTool to fetch JSON Web Key Set for OpenID Connect. Use when verifying Loyverse ID token signatures.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_MERCHANT_INFOTool to get merchant information. Use after authenticating to retrieve merchant account details.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_MODIFIERTool to get a single modifier by ID. Use when you need to fetch details of an existing modifier in Loyverse.
Input parameters
UUID of the modifier to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_OPEN_ID_CONFIGURATIONTool to retrieve the OpenID Connect discovery document. Use when integrating authentication and need endpoints and supported features.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_PAYMENT_TYPETool to get a single payment type by its ID. Use when you need to fetch full details of a specific payment method before processing a transaction.
Input parameters
The unique ID of the payment type to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_POS_DEVICETool to retrieve details of a specific POS device by its ID. Use when you need POS device metadata after obtaining the device ID.
Input parameters
The unique ID of the POS device to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_RECEIPTTool to retrieve a single receipt by its receipt number. Use when you need detailed information about a specific receipt including line items, payments, and totals.
Input parameters
The unique receipt number to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_STORETool to retrieve details of a specific store by its ID. Use when you need store metadata (address, contact) after obtaining the store ID.
Input parameters
The unique ID of the store to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_SUPPLIERTool to get a single supplier by their ID. Use when you need to fetch details of a specific supplier in Loyverse.
Input parameters
The unique UUID of the supplier to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_TAXTool to get a single tax by ID. Use when you need to retrieve details of a specific tax configuration in Loyverse.
Input parameters
The unique ID of the tax to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_VARIANTTool to get a single item variant by its ID. Use when you need detailed information about a specific variant from the Loyverse inventory.
Input parameters
The unique UUID of the variant to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_GET_WEBHOOKTool to get a single webhook by its ID. Use when you need to retrieve details of a specific webhook configuration.
Input parameters
The unique UUID of the webhook to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_CATEGORIESTool to list categories with optional filtering and pagination.
Input parameters
Maximum number of categories to return (1-250). Default is 50.
Cursor for pagination from a previous response
Include soft-deleted categories when true
Comma-separated list of category UUIDs to filter by (e.g., 'uuid1,uuid2')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_CUSTOMERSTool to get a list of customers. Use when you need paginated customer lists with optional filters.
Input parameters
Filter by customer's email address (exact match).
Maximum number of customers to return per request (1-250). Default is 50 if not specified.
Cursor for pagination. Use the cursor value from the previous response to fetch the next page of results.
Filter by a specific customer ID to retrieve that customer's details.
Filter by customer's phone number. Include country code for best results.
Filter customers created at or before this timestamp (ISO 8601 format).
Filter customers created at or after this timestamp (ISO 8601 format).
Filter customers updated at or before this timestamp (ISO 8601 format).
Filter customers updated at or after this timestamp (ISO 8601 format).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_DISCOUNTSTool to list discounts. Use when fetching a paginated set of discounts for display or sync.
Input parameters
Maximum number of discounts to return (>=1).
Number of discounts to skip for pagination (>=0).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_EMPLOYEES2Tool to get a list of employees with advanced filtering options. Use when you need to filter employees by creation/update dates or view deleted employees.
Input parameters
Used for pagination. Number of employees to return per page.
Used for pagination. Cursor for pagination; pass value from previous response to fetch next page
Return only employees specified by a comma-separated list of IDs
Show deleted modifiers and modifier options
Show resources created before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources created after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_INVENTORYRetrieves inventory levels for item variants across stores in the Loyverse system. Use this to track stock quantities for specific variants at different store locations. Filter by store IDs, variant IDs, or date range to narrow results.
Input parameters
Maximum number of inventory levels to return per page. Default is 50, maximum is 250.
Pagination cursor from a previous response. Pass this value to retrieve the next page of results.
Comma-separated list of store IDs (UUIDs) to filter inventory levels. Only inventory for these stores will be returned.
Comma-separated list of variant IDs (UUIDs) to filter inventory levels. Only inventory for these variants will be returned.
Return only inventory levels updated on or before this ISO 8601 timestamp.
Return only inventory levels updated on or after this ISO 8601 timestamp.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_ITEMSRetrieves a paginated list of items (products) from the Loyverse inventory. Items are sorted by creation date in descending order (newest first). Use filters to narrow results by category, date range, or specific item IDs.
Input parameters
Maximum number of items to return per page. Default is 50, maximum is 250.
Pagination cursor from a previous response to retrieve the next page of results.
Comma-separated list of item IDs (UUIDs) to filter by.
Filter items by category ID (UUID).
If true, include soft-deleted items in the response. Default is false.
Return only items created on or before this ISO 8601 timestamp.
Return only items created on or after this ISO 8601 timestamp.
Return only items updated on or before this ISO 8601 timestamp.
Return only items updated on or after this ISO 8601 timestamp.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_MODIFIERS2Tool to get a list of modifiers sorted by created_at in descending order. Use when you need to retrieve modifiers with advanced filtering options including creation/update dates and deleted items.
Input parameters
Used for pagination. Number of modifiers to return per page (1-250)
Used for pagination. Cursor for pagination; use value from previous response to fetch next page
Return only modifiers specified by a comma-separated list of IDs
Show deleted modifiers and modifier options
Show resources created before date (ISO 8601 format)
Show resources created after date (ISO 8601 format)
Show resources updated before date (ISO 8601 format)
Show resources updated after date (ISO 8601 format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_PAYMENT_TYPESTool to list payment types. Use when you need to fetch available payment methods with optional filters and pagination.
Input parameters
Maximum number of payment types to return (1-250)
Cursor for pagination; pass value from previous response to retrieve next page
Whether to include soft-deleted payment types
Only include payment types created at or before this ISO 8601 timestamp
Only include payment types created at or after this ISO 8601 timestamp
Only include payment types updated at or before this ISO 8601 timestamp
Only include payment types updated at or after this ISO 8601 timestamp
Comma-separated list of payment type UUIDs to filter results
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_POS_DEVICESTool to get a list of POS devices sorted by creation date in descending order. Use when you need to retrieve POS device information for store management or reporting.
Input parameters
Maximum number of POS devices to return per page (1-250). Default is 50.
Pagination cursor from a previous response. Use to fetch the next page of results.
Filter POS devices by store ID (UUID). If not provided, returns devices from all stores.
If true, include soft-deleted POS devices in the response. Default is false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_RECEIPTSTool to retrieve a list of receipts. Use when you need to fetch receipts with optional filters and handle pagination.
Input parameters
Maximum number of receipts to return (1-250)
Filter receipts by order ID
Cursor for pagination; pass value from previous response to fetch next page
Filter receipts by source application
Filter receipts by store ID
Include receipts created before this ISO 8601 date/time
Include receipts created at or after this ISO 8601 date/time
Include receipts updated before this ISO 8601 date/time
Include receipts updated at or after this ISO 8601 date/time
Comma-separated list of receipt numbers to filter results
Return only receipts after this receipt number
Return only receipts before this receipt number
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_SHIFTSTool to list shifts. Use when you need to retrieve shift records for reporting or auditing with optional filters.
Input parameters
Maximum number of shifts to return (1-250)
Cursor for pagination; use the cursor from previous response to fetch next page
Comma-separated list of store IDs to filter shifts
Show shifts opened before this date/time (ISO 8601)
Show shifts opened at or after this date/time (ISO 8601)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_STORESTool to get a list of stores sorted by creation date (newest first). Use when you need to retrieve store information across multiple locations.
Input parameters
Maximum number of stores to return per page (1-250). Default is 50.
Pagination cursor from a previous response. Use to fetch the next page of results.
Return only stores specified by a comma-separated list of IDs.
If true, include deleted stores in the response. Default is false.
Show stores created on or before this timestamp (ISO 8601 format).
Show stores created on or after this timestamp (ISO 8601 format).
Show stores updated on or before this timestamp (ISO 8601 format).
Show stores updated on or after this timestamp (ISO 8601 format).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_SUPPLIERSTool to retrieve a list of suppliers. Use when you need a paginated supplier directory with optional filters.
Input parameters
Maximum number of suppliers to return (1-250). Default is 50.
Pagination cursor from a previous request. Use to fetch the next page.
Whether to include soft-deleted suppliers in the results.
Return only suppliers specified by a comma-separated list of IDs
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_TAXES2Tool to get a list of taxes sorted by creation date (newest first). Use when you need to retrieve tax records with optional filtering by IDs or date ranges.
Input parameters
Return only taxes specified by a comma-separated list of IDs
Show deleted modifiers and modifier options
Show resources created before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources created after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_VARIANTS2Tool to get a list of item variants sorted by creation date (newest first). Use when you need comprehensive filtering by variant IDs, item IDs, SKU, or date ranges, including deleted variants.
Input parameters
Filter variants by SKU (Stock Keeping Unit) code
Maximum number of variants to return per page. Used for pagination. Default is 50.
Pagination cursor from a previous response. Used for pagination.
Return only variants attached to specified item IDs (comma-separated UUIDs)
Show deleted modifiers and modifier options. Default is false.
Return only variants specified by a comma-separated list of variant IDs (UUIDs)
Show resources created before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources created after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated before date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Show resources updated after date (ISO 8601 format, e.g: 2020-03-30T18:30:00.000Z)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_LIST_WEBHOOKSTool to list webhooks. Use when you need to retrieve all configured webhooks.
Input parameters
Maximum number of webhooks to return per page.
Number of webhooks to skip for pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_UPDATE_INVENTORYTool to batch update inventory levels for item variants at specific stores. Use when you need to set absolute stock quantities (not deltas) for one or more variant-store combinations.
Input parameters
List of inventory level updates to apply. Each entry specifies a variant, store, and new stock level.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LOYVERSE_UPLOAD_ITEM_IMAGETool to upload a single image for an item. Accepts image/png or image/jpeg content types. Use after confirming the item ID to upload product images.
Input parameters
Image file to upload. Accepts image/png or image/jpeg content types.
The unique UUID of the item to upload the image to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 67 agents privately built on Nagent that already use Loyverse.
Build on Nagent
Connect Loyverse to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Loyverse, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Loyverse is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Loyverse is connected, you configure its 58 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Loyverse steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Loyverse event fires, the agent kicks off automatically.
Every Loyverse action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Loyverse ships with 58 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Loyverse together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Loyverse-based workflows tailored to your business.