Glossary

What is a webhook?

A webhook is an event-driven notification sent from one system to an agreed web address in another system. It lets the receiving application react when something changes, rather than repeatedly asking whether new data is available. A webhook may carry the changed data or only enough information for the receiver to retrieve it.

Responding to a product event

A system can publish events such as a product being approved, an asset changing or an export completing. The receiving endpoint processes the event according to the integration design. The event name and payload do not automatically define the full business workflow.

For example, a product approval event from a PIM could tell an integration service to retrieve the approved record and prepare a channel update. The service still needs to map the data, check destination requirements and record the result.

Plan for delivery and processing failures

A webhook notification is not proof that the destination completed the intended update. Networks, queues and receiving services can fail. The integration needs an explicit policy for authentication, retries, duplicate events and events that arrive after newer changes.

Define what identifies an event and a product version, and retain enough history to investigate missed updates. Where appropriate, a periodic reconciliation can detect differences that event delivery alone has not resolved. Webhooks and APIs commonly work together: the webhook signals a change and an API supplies or updates the relevant data.

Related terms

Sources and further reading

Product Data Services

Explore practical support for organising, improving and maintaining product information.