Purpose

This page explains what a webhook is, why Skulytics provides webhook support, and how clients can use webhooks to receive real-time event updates from their Skulytics account.

What Is a Webhook?

A webhook is an automated HTTP callback that is triggered by an event in one system and sends data to another system in real time. Unlike a standard API, which requires a client to send a request before receiving data, a webhook automatically pushes data as soon as an event occurs. This makes webhooks useful for real-time notifications and data synchronization between connected systems.

Why Use Webhooks?

Once a webhook is registered, Skulytics automatically sends event data to the client’s webhook endpoint whenever supported activity occurs in the account. Webhook events are delivered as a JSON payload containing an event object. Clients can use these events to keep their systems up to date with changes such as: product status updates pricing updates LAP (Lowest Advertised Price) and LCP (Lowest Cart Price) updates newly released products updated product information

How Webhooks Work

When a supported event occurs in Skulytics, Skulytics sends an HTTP POST request to the client’s registered webhook endpoint. Each request contains a JSON payload with an event object. The client’s system is expected to:

receive the POST request
parse the JSON payload
acknowledge successful receipt by returning an HTTP 200 OK response

Getting Started

To start receiving webhook events, clients must complete the following steps:

Build a webhook endpoint

Create an endpoint in your application that accepts HTTP POST requests with a JSON payload.

For local development, an HTTP endpoint may be used. For production use, HTTPS should be used to ensure secure data transmission.
Register the endpoint

To register a webhook endpoint, contact Skulytics Support for authorization.

Each client can register one webhook endpoint.

Webhook Endpoint Requirements

A valid webhook endpoint must:
- accept HTTP POST requests
- receive a JSON payload containing the webhook event object
- return an HTTP 200 OK response after the event is received

Webhook Retry Behavior

Skulytics supports webhook retry behavior for delivery attempts that are not successfully completed.

The retry schedule is as follows:

Initial attempt: sent immediately
First retry: after 10 minutes
Second retry: after 30 minutes
Final status: if the second retry also fails, the webhook is marked as failed

Retry can be enabled or disabled for each registered webhook.

Webhook URL Format

The registered webhook URL should follow this format:

https://client-website.com/your-webhook-endpoint

Example:

Available Webhook Event Types

Skulytics currently supports the following webhook event categories:

Product Status Update
Pricing Update
LAP and LCP Update
New Product
Update Product

Related Pages

For details about the updated webhook acknowledgment mechanism that will go live on April 23 and fully replace the previous mechanism on May 1, see Webhook Migration Guide.