Product Webhook API
Product Webhook API is an event-based API that lets our partners be notified about all product changes events, including new products added to our repository, product changes (including price or stock changes) but also changes within partner's shop and collections.
It is an event-based API, meaning that all small changes will be sent out to the subscriber, upon which the subscriber can react accordingly to ie. invalidate your own cache, update the product prices that you keep in your system or reindex any third party searches/indices. This is a great way to keep your snapshot of Tipser's inventory up to date if combined with Export Feed API.
In order to get subscribed to the Webhook API, reach out to the support team with your webhook URL and a list of events that you want to subscribe to. Our Webhook API is using a POST HTTP method, so be sure to use the proper method type.
As soon as the webhook URL you provided is up and running, the first message will be delivered which requires confirmation of the subscription.
The first message will look as follows:
To confirm the subscription, as soon as the subscription event is received, you must callback the address at SubscribeURL field (simple GET request will do).
From now on the events will be delivered to your webhook listener. The request will look as follows:
The event will be called whenever the product price, stock, title has changed, but also when it got sold out or it got new variants added. It is also triggered when a new product is added to our inventory. If you subscribe to this one, expect a massive amount of events if you are subscribed to the whole market inventory without any filters.
It is triggered whenever a product in one of POS collection has been changed. It will trigger for all product changes, no matter if it's the price or the description. This event may be verbose.
Similarly to the product-changed event, it is triggered on exactly same circumstances but only if it is contained in one of POS collection.
It is triggered when either a new collection has been added to the shop or removed from the shop of the POS.
Payload will contain snapshot of all the collection ids currently visible in shop.
It is triggered whenever a visible collection of the POS has been changed (it's name or friendly url was modified). Private collections will not trigger that event.
It is triggered whenever a new collection has been added to POS' shop. Private collections will not trigger that event.