Loyverse

Delete Category via DELETE /categories/{category_id}

Delete Customer via DELETE /customers/{customer_id}

Delete Discount via DELETE /discounts/{discount_id}

Delete Item via DELETE /items/{item_id}

Delete a single image via DELETE /items/{item_id}/image

Delete Modifier via DELETE /modifiers/{modifier_id}

Delete POS Device via DELETE /pos_devices/{pos_device_id}

Delete Supplier via DELETE /suppliers/{supplier_id}

Delete Tax via DELETE /taxes/{tax_id}

Delete Item Variant via DELETE /variants/{variant_id}

Delete Webhook via DELETE /webhooks/{webhook_id}

The list of categories is sorted by created_at property in descending order. The most recent categories appear first via GET /categories

Get a single category via GET /categories/{category_id}

The list of customers is sorted by created_at property in descending order. The most recent customers appear first via GET /customers

Get a single customer via GET /customers/{customer_id}

The list of discounts is sorted by created_at property in descending order. The most recent discounts appear first via GET /discounts

Get a single discount via GET /discounts/{discount_id}

The list of employees is sorted by created_at property in descending order. The most recent employees appear first via GET /employees

Get a single employee via GET /employees/{employee_id}

Inventory levels for item variants via GET /inventory

The list of items is sorted by created_at property in descending order. The most recent items appear first via GET /items

Get a single item via GET /items/{item_id}

Get merchant information via GET /merchant/

The list of modifiers is sorted by created_at property in descending order. The most recent modifiers appear first via GET /modifiers

Get a single modifier via GET /modifiers/{modifier_id}

The list of payment types is sorted by created_at property in descending order. The most recent payment types appear first via GET /payment_types

Get a single payment type via GET /payment_types/{payment_type_id}

The list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first via GET /pos_devices

Get a single pos device via GET /pos_devices/{pos_device_id}

The list of receipts is sorted by created_at property in descending order. The most recent receipts appear first via GET /receipts

Get a single receipt via GET /receipts/{receipt_number}

The list of shifts is sorted by created_at property in descending order. The most recent shifts appear first via GET /shifts

Get a single shift via GET /shifts/{shift_id}

The list of stores is sorted by created_at property in descending order. The most recent stores appear first via GET /stores

Get a single store via GET /stores/{store_id}

The list of suppliers is sorted by created_at property in descending order. The most recent suppliers appear first via GET /suppliers/

Get a single supplier via GET /suppliers/{supplier_id}

The list of taxes is sorted by created_at property in descending order. The most recent taxes appear first via GET /taxes

Get a single tax via GET /taxes/{tax_id}

The list of variants is sorted by created_at property in descending order. The most recent variants appear first via GET /variants

Get a single item variant via GET /variants/{variant_id}

This endpoint will only return webhooks created by the application which is making the request. via GET /webhooks/

Get a single webhook via GET /webhooks/{webhook_id}

Create or update a single category via POST /categories

Create or update a single customer via POST /customers

Create or update a single discount via POST /discounts

Batch update inventory levels for item variants via POST /inventory

Create or update a single item via POST /items

Create or update a single modifier via POST /modifiers

Create or update a single pos device via POST /pos_devices

Create a sales receipt via POST /receipts

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. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. * Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. * If a refund is created successfully, it will cause a restock of items specified in a refund receipt. via POST /receipts/{receipt_number}/refund

Create or update a single supplier via POST /suppliers/

Create or update a single tax via POST /taxes

Create or update a single variant via POST /variants

Create or update a single webhook via POST /webhooks/