This guide preserves published Enad setup and compatibility guidance. Enad app is authoritative for current controls. Use generated API/OpenAPI reference and the Event catalog for exact fields, payloads, authentication, and delivery behavior; examples and operational limits below are compatibility guidance until attached to those contracts.

The Webhooks integration sends selected Enad events to a custom HTTP endpoint.

This page covers outgoing events configured under System → Integrations. The separate System → Webhooks page is used for incoming provider webhooks.

Storefront revalidate provides a dedicated workflow for storefront cache revalidation.

Requirements

Required configuration:

• A publicly reachable HTTPS endpoint.
• Event types delivered to the endpoint.
• An optional authentication header name and value.

Configuration

Configuration follows the common integration setup and includes the endpoint and enabled events.

Supported event types cover products, stocks, prices, variants, categories, tags, markets, attributes, store groups, users, organisations, brands, and series.

Additional settings include:

• Store group filters for price-update deliveries.
• Market filters for price-update deliveries.
• Delivery delay.

Empty market or store group filters include matching updates for all markets or store groups.

Connection checks are available under Status → Integration validation. The refresh control runs the checks again.

Authentication

Enad adds the configured header to each request. Supported patterns include Authorization with a bearer token and custom headers such as x-api-key.

The header value is a secret and should be rotated if exposed.

Event payloads and delivery

See Events for supported event families, payload structure, acknowledgement requirements, ordering, and retries.