1. Home
  2. Docs
  3. Current
  4. Guides
  5. TIKI Theory
  6. Event type

Event type

Current supported event type

  • ORDER_CREATED_SUCCESSFULLY

This event indicate that an order was created from your products, so you can handle it accordingly to the order’s
operation mode. The event only fired when the order reach the queueing status, it mean the order
placed successfully from buyer and Tiki system.

v1 Payload:

FieldTypeExampleDescription
order_codeString239545064order’s code the new order just created.
statusStringshippingThe current status of the order

Mock order v2 work with this event also.

  • ORDER_STATUS_UPDATED

This event indicate an order status was get update either by tiki or seller you can like handle the logistic accordingly
or get notification about delivery journey of the order. Refer order status here

v1 Payload:

FieldTypeExampleDescription
order_codeString239545064order’s code the new order just created.
statusStringshippingThe current status of the order

Mock order v2 work with this event also.

  • PRODUCT_PRICE_UPDATED

This event indicate that price of your’s product have changed.

v1 Payload:

FieldTypeExampleDescription
product_idInteger239545064The product id of product has price changed
original_skuStringxyz_abcThe seller’s sku of the product
price_fromString239545064The price change from this price
price_toString239545064The price change to this price, that’s current price of product
  • PRODUCT_MARKET_PRICE_UPDATED

This event indicate that market price of your’s product have changed.

v1 Payload:

FieldTypeExampleDescription
product_idInteger239545064The product id of product has price changed
original_skuStringxyz_abcThe seller’s sku of the product
market_price_fromString239545064The market price change from this price
market_price_toString239545064The market price change to this price, that’s current market price of product
  • PRODUCT_INVENTORY_UPDATED

This event indicate that inventory of your product have changed. Not all the quantity will changed in one event, so you
can implement simple check from and to to do your logic.

v1 Payload:

⚠️ Deprecate from 2022 January 04

The v1 event will get removed from 04/Jan because Tiki move to multiple warehouses model. Please use v2 below instead

FieldTypeExampleDescription
product_idInteger239545064The product id of product has price changed
original_skuStringxyz_abcThe seller’s sku of the product
quantity_toInteger50The setting quantity change from
quantity_fromInteger50The setting quantity change to
quantity_sellable_fromInteger50The sellable quantity change from
quantity_sellable_toInteger49The sellable quantity change to
quantity_available_fromInteger50The avaiable quantity change from
quantity_available_toInteger50The available quantity change to
quantity_reserved_fromInteger0The reserved quantity change from
quantity_reserved_toInteger1The reserved quantity change to

v2 Payload:

The inventory changed events according to each warehouse of products. You can see the new field warehouse_id. It’s your warehouse that the product inventory actually changed. Note it will only have events after 04/Jan

FieldTypeExampleDescription
warehouse_idLong1034The warehouse that change inventory.
product_idLong239545064The product id of product has price changed
original_skuStringxyz_abcThe seller’s sku of the product
quantity_toInteger50The setting quantity change from
quantity_fromInteger50The setting quantity change to
quantity_sellable_fromInteger50The sellable quantity change from
quantity_sellable_toInteger49The sellable quantity change to
quantity_available_fromInteger50The avaiable quantity change from
quantity_available_toInteger50The available quantity change to
quantity_reserved_fromInteger0The reserved quantity change from
quantity_reserved_toInteger1The reserved quantity change to
Was this article helpful to you? Yes No

How can we help?

Leave a Reply

Your email address will not be published.