Loyverse integration: operations for AI agents
Loyverse connects to Type.com as an integration. This page lists the 57 operations documented for Claude and Codex in Type.com: 32 read, 14 write, 11 destructive.
About Loyverse
Loyverse is a point-of-sale (POS) system designed for small businesses, offering features like sales management, inventory tracking, and customer engagement tools.
Categories: Commerce & Payments
How to connect Loyverse to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
57 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
57 operations listed.
Webhooks
- Read
Get a single webhook
GET /webhooks/{webhook_id}
- Read
Get a list of webhooks
This endpoint will only return webhooks created by the application which is making the request.
- Write
Create or update a single webhook
POST /webhooks/
- Destructive
Delete a single resource
DELETE /webhooks/{webhook_id}
Merchant
- Read
Get merchant information
GET /merchant/
Suppliers
- Read
Get a single supplier
GET /suppliers/{supplier_id}
- Read
Get a list of suppliers
The list of suppliers is sorted by createdat property in descending order. The most recent suppliers appear first
- Write
Create or update a single supplier
POST /suppliers/
- Destructive
Delete a single resource
DELETE /suppliers/{supplier_id}
Categories
- Read
Get a single category
GET /categories/{category_id}
- Read
Get a list of categories
The list of categories is sorted by createdat property in descending order. The most recent categories appear first
- Write
Create or update a single category
POST /categories
- Destructive
Delete a single resource
DELETE /categories/{category_id}
Customers
- Read
Get a single customer
GET /customers/{customer_id}
- Read
Get a list of customers
The list of customers is sorted by createdat property in descending order. The most recent customers appear first
- Write
Create or update a single customer
POST /customers
- Destructive
Delete a single resource
DELETE /customers/{customer_id}
Discounts
- Read
Get a single discount
GET /discounts/{discount_id}
- Read
Get a list of discounts
The list of discounts is sorted by createdat property in descending order. The most recent discounts appear first
- Write
Create or update a single discount
POST /discounts
- Destructive
Delete a single resource
DELETE /discounts/{discount_id}
Employees
- Read
Get a single employee
GET /employees/{employee_id}
- Read
Get a list of employees
The list of employees is sorted by createdat property in descending order. The most recent employees appear first
Inventory
- Read
Inventory levels for item variants
GET /inventory
- Write
Batch update inventory levels for item variants
POST /inventory
Items
- Read
Get a single item
GET /items/{item_id}
- Read
Get a list of items
The list of items is sorted by createdat property in descending order. The most recent items appear first
- Write
Upload a single image
You can download image directly using image/png requests with image data. The following is an example of such an HTTP request: POST /v1.0/{itemid}/image Content-Type: image/png Content-Length: 1000 [file content goes there]
- Write
Create or update a single item
POST /items
- Destructive
Delete a single resource
DELETE /items/{item_id}
- Destructive
Delete a single image
DELETE /items/{item_id}/image
Modifiers
- Read
Get a single modifier
GET /modifiers/{modifier_id}
- Read
Get a list of modifiers
The list of modifiers is sorted by createdat property in descending order. The most recent modifiers appear first
- Write
Create or update a single modifier
POST /modifiers
- Destructive
Delete a single resource
DELETE /modifiers/{modifier_id}
Payment types
- Read
Get a single payment type
GET /payment_types/{payment_type_id}
- Read
Get a list of payment types
The list of payment types is sorted by createdat property in descending order. The most recent payment types appear first
POS devices
- Read
Get a single pos device
GET /pos_devices/{pos_device_id}
- Read
Get a list of pos devices
The list of pos devices is sorted by createdat property in descending order. The most recent pos devices appear first
- Write
Create or update a single pos device
POST /pos_devices
- Destructive
Delete a single resource
DELETE /pos_devices/{pos_device_id}
Receipts
- Read
Get a single receipt
GET /receipts/{receipt_number}
- Read
Get a list of receipts
The list of receipts is sorted by createdat property in descending order. The most recent receipts appear first
- Write
Create a sales receipt
POST /receipts
- Write
Create a refund receipt
When using the refund API you should take into account these notes: At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment.
Shifts
- Read
Get a single shift
GET /shifts/{shift_id}
- Read
Get a list of shifts
The list of shifts is sorted by createdat property in descending order. The most recent shifts appear first
Stores
- Read
Get a single store
GET /stores/{store_id}
- Read
Get a list of stores
The list of stores is sorted by createdat property in descending order. The most recent stores appear first
Taxes
- Read
Get a single tax
GET /taxes/{tax_id}
- Read
Get a list of taxes
The list of taxes is sorted by createdat property in descending order. The most recent taxes appear first
- Write
Create or update a single tax
POST /taxes
- Destructive
Delete a single resource
DELETE /taxes/{tax_id}
Variants
- Read
Get a single item variant
GET /variants/{variant_id}
- Read
Get a list of item variants
The list of variants is sorted by createdat property in descending order. The most recent variants appear first
- Write
Create or update a single variant
POST /variants
- Destructive
Delete a single resource
DELETE /variants/{variant_id}
No operations match.
See How connections work for access and permissions, or browse all integrations.