Stay up-to-date proactively with Product Change Notifications
The PCN (Product Change Notifications) are http calls performed by Tiqets to your server, to notify you about products going off-sale, becoming available again, or when their content is changed.
This section describes Tiqets new Product Change Notifications system, launched in November 2025.
We are still supporting the old PCN system for now, and if you still use it and need help you can find its description there: [Deprecated] PCN API
Introduction
By explicitly subscribing to PCN for specific products you ensure notifications are relevant for your business.
Each notification informs you about what type of change a product has undergone, and includes helpful type-specific information, such as estimated reopening time frames or a suggested fallback product you can promote. This allows you to keep your catalogue and content accurate, avoid promoting unavailable options, and continue offering relevant alternative.
Read the guideline below to find 1- what notifications are sent, 2- how to subscribe to notifications, and 3- how to handle the notifications & web-hook security.
Which notifications are sent?
When a product’s content or sale status changes, notifications are sent. This typically means:
the product's description, or another aspect such as variants, has changed;
a product that was available for booking becomes unavailable;
a previously unavailable product becomes available again.
We send one separate notification per product when something changes, but if a product undergoes multiple changes at once the notification can contain multiple changes objects.
For each change, the type of event is described by the change_type field. The type can be checkout_disabled, checkout_enabled and product_details_update. Each type comes with its own set of relevant fields:
when a product becomes unbookable, we also provide you with a reason, an expected reopening timeframe, and an alternative product so you don't waste time trying to sell a disabled product and can instead switch to an available similar product;
when a product becomes bookable again, there's no additional information;
when a product content is changed, we give you the field's name & type, and the old & new values so you can easily update your website. These can cover description, what's included, variant list, tags, exhibitions, starting time, languages, etc.
Example
Here's an example of a checkout_disabled type change notification.
Notification delays
Notifications are not sent instantly. The notifications for products will be held for several minutes, to avoid spamming you when multiple mutations are being done to the same product. Only the last mutation of the same type will be sent to you.
See full description of the webhooks here: [new] Product Change Notifications
Subscribing to PCN
To start receiving product change updates, you need to create a subscription. Subscriptions define which products you want to monitor, which notifications you're interested in, and where Tiqets should send the notifications.
Create a subscription
Example:
Each subscription specifies:
a Subscription ID that you choose yourself and that allows you to track your subscriptions;
where you want to receive our notifications: the
callback_url;which change types you're interested in, with the field
change_types(you can select the typescheckout_disabled,checkout_enabledand/orproduct_details_update);which products you want to receive notifications about. There's different ways you can select one or multiple products and with the field
subscription_typeyou can choose how to select products:the
product_idsoption means you'll have to provide the IDs of specific products inentity_ids;the
experience_idsoption means you'll have to provide the IDs of experiences inentity_idsand we will send you notifications for all the products that are in these experiences;another option that we'll add soon will be useful to subscribe for all the products that you have sold more than 5 times in the past 12 months.
You can create one subscription with multiple products, or multiple subscriptions. For example, you might want separate subscriptions for your different markets or to separate high-priority and low-priority products.
After creating the subscription, you will start receiving notifications for the selected products.
Manage your subscriptions
You can also manage your existing PCN subscription using the Tiqets Distributor API.
See endpoints full technical description here: [New] Product Change Notifications API.
How to handle the notifications
When a product change is detected, Tiqets sends a POST request to the endpoint you specified while subscribing. This request contains a JSON payload such as this one:
Your system should be prepared to:
Acknowledge the notification Return an HTTP 200 response to confirm successful delivery. If your server does not respond with a 200 status code, Tiqets will retry a few times and if it keeps failing we'll mark your subscription as
degraded. After a month in this status, your subscription will becancelled. Note: the response body is ignored; only the HTTP status code matters.Update your catalog based on the notification The notification payload contains all the information needed to update the product’s content or sale status immediately. You should deactivate products that became unavailable, and when a
recommended_alternative_product_idis provided, consider promoting the suggested fallback product to maintain your conversion flow and avoid losing sales.Use the additional context to plan ahead You can also make use of the following fields to improve your catalog management:
reason: Optionally display or log why the product is unavailable (e.g., seasonal closure).expected_reopening: Plan when to relist the product based on its expected return timeframe (and/or just watch out for thecheckout_enablednotification).
Webhook Security
Managing subscriptions requires you to sign your requests, but no authentication mechanism applies to the HTTP calls Tiqets performs to you. For webhooks to work you need to open up one or multiple endpoints that are publicly accessible.
To ensure those endpoint(s) don't get abused, here are two suggestions for increased security:
Whitelist our outgoing IP addresses (see list below);
Use very hard-to-guess URLs when subscribing to notifications, such as
https://mydomain.com/webhooks/tiqets/ieAsjDlcm67hJacH643Ahc/. You could even update that URL periodically.
99.80.191.99 (out.acceptance.steq.it)
63.35.71.28 (out.acceptance.steq.it)
63.35.56.49 (out.acceptance.steq.it)
99.81.16.132 (out.tiqets.com)
54.77.55.83 (out.tiqets.com)
34.246.210.158 (out.tiqets.com)
Last updated
Was this helpful?

