Guides
Subscribe to updatesSupport website

Entities and events

daily_closings

events:

  • CREATED: event generated every time the daily closing is performed.

type of entity: see example on the example page

items

events:

  • CREATED: event generated every time an item is created
  • UPDATED:  event generated every time an item is updated
  • DELETED:  event generated every time an item is deleted

type of entity: Items

customers

events:

  • CREATED: event generated every time a customer is created
  • UPDATED: event generated every time a customer is updated
  • DELETED: event generated every time a customer is deleted

type of entity: Customers

suppliers

events:

  • CREATED: event generated every time a supplier is created
  • UPDATED: event generated every time a supplier is updated
  • DELETED: event generated every time a supplier is deleted

type of entity: Suppliers

sales

events:

  • CREATED: event generated every time a sale is created. It considers also the case when an order is sent to till
  • UPDATED: event generated every time a sale is updated
  • DELETED: event generated every time a sale is deleted
  • CLOSED: event generated every time a receipt or invoice is issued

type of entity: sales

orders

Deprecation Notice : The orders endpoint will be deprecated on July 1, 2024, sending orders can be done even faster with the sales endpoint
Returns a Json with all orders of selected shop.
An order can be in open or closed status. If is open it can be edited. Each order can contain a 'previus_order' that is the previous version of the order, before last save (parcheggia) or print.

events:

  • CREATED: event generated every time a order is created
  • UPDATED: event generated every time a sale is updated. From Tilby application can occur when the order is changed, parked or printed.
  • DELETED:  event generated every time a order is deleted
  • CLOSED: event generated every time the receipt for the order is issued

type of entity: order

bookings

events:

  • CREATED: event generated every time a booking is created
  • UPDATED: event generated every time a booking is updated
  • DELETED: event generated every time a booking is deleted

type of entity: booking

stock_movements

events:

  • CREATED: event generated every time an manual stock movement is performed

type of entity: stock_movement

stock

events:

  • UPDATED: event generated every time the stock on an item is changed. For example when a transaction is closed and in that there are items with a stock reserve set in Tilby, or if a manual stock movement is created.

type of entity: see example on the example page

rooms

events:

  • CREATED: event generated every time a table room is created
  • UPDATED: event generated every time a table room is updated
  • DELETED: event generated every time a table room is deleted

type of entity: rooms

fidelities_movements

events:

  • CREATED : event generated every time a fidelity movement is automatically or manually created.

type of entity fideliy_movement

fidelities_points

events:

  • UPDATED: event generated every time the loyalty point balance of a customer is updated

type of entity: fidelity_points

channels

events:

  • CREATED: event generated every time a channel is created
  • UPDATED: event generated every time a channel is updated
  • DELETED: event generated every time a channel is deleted

type of entity: channel

departments

events:

  • CREATED: event generated every time a department is created
  • UPDATED: event generated every time a department is updated
  • DELETED: event generated every time a department is deleted

type of entity: see example on the example page

categories

events:

  • CREATED: event generated every time a category is created
  • UPDATED: event generated every time a category is updated
  • DELETED: event generated every time a category is deleted

type of entity: see example on the example page

giftcards

events:

  • CREATED: event generated every time a giftcards is created
  • UPDATED: event generated every time a giftcards is updated. A movement on a giftcards will generate this event
  • DELETED: event generated every time a giftcards is deleted

type of entity: see example on the example page

giftcards_types

events:

  • CREATED: event generated every time a giftcards_types is created
  • UPDATED: event generated every time a giftcards_types is updated
  • DELETED: event generated every time a giftcards_types is deleted

type of entity: see example on the example page

prepaid_movements

events:

  • UPDATED: event generated every time a prepaid movements is generated. "credit" is the total amount available for the customer

type of entity: see example on the example page

Updated 7 months ago