Purpose

This page explains the changes to the Skulytics webhook acknowledgment mechanism and the actions clients must take before the previous mechanism is officially removed.

Overview

Skulytics is introducing an updated webhook acknowledgment mechanism.

The registered webhook endpoint URL will remain the same. Existing webhook retry behavior also remains unchanged.

What will change is how Skulytics handles acknowledgment timing from the client endpoint. Clients must ensure that their webhook endpoint returns an acknowledgment immediately and does not delay the response with heavy or blocking processing.

Effective Dates

The updated webhook acknowledgment mechanism will go live on April 23.

From April 23 to April 30, clients may still use the previous webhook handling mechanism during the transition period.

Starting May 1, the previous webhook mechanism will be officially removed, and clients must follow the new acknowledgment requirements.

Timeline

New mechanism goes live: April 23
Previous mechanism still supported until: April 30
Previous mechanism officially removed: May 1

What Is Changing

Under the previous webhook mechanism, Skulytics could continue waiting for heavy client-side processing to complete before continuing the webhook flow.

Starting with the new mechanism, clients must return an HTTP 200 OK acknowledgment within the allowed time window.

Under the new mechanism:

the client endpoint must acknowledge the webhook request immediately
heavy or long-running processing must not block the acknowledgment response
Skulytics will only wait up to 10 seconds for acknowledgment
if acknowledgment is not received within 10 seconds, Skulytics stops waiting for that delivery attempt

What Is Not Changing

The following items remain unchanged:

the registered webhook endpoint URL
the use of HTTP POST requests
the JSON payload format for webhook events
the supported webhook event categories
the existing webhook retry behavior

Required Client Action

Before May 1, clients should review and update their webhook implementation to ensure that:

the endpoint accepts incoming HTTP POST webhook requests
the endpoint returns an HTTP 200 OK response immediately after receiving the webhook event
webhook acknowledgment is not delayed by heavy processing
acknowledgment is returned within 10 seconds

Clients are strongly encouraged to complete these changes before April 23, when the new mechanism goes live.

Webhook Processing Requirements

**Fast Acknowledgment **

The webhook endpoint should acknowledge the request immediately after the event is received.

No Blocking Processing in the Response Flow

Heavy processing should not delay the webhook response.

Examples of processing that should not block the acknowledgment response include:

large database operations
long-running business logic
external API calls that may take time
other slow or resource-intensive processing

Acknowledgment Time Limit

Recommended webhook acknowledgment timing:

Preferred: ≤ 1 second
Maximum: ≤ 10 seconds

Starting April 23, Skulytics requires webhook acknowledgments to be returned within 10 seconds. If the client endpoint does not respond within this time limit, Skulytics stops waiting for that delivery attempt.

The previous webhook handling mechanism will remain available only until April 30. Starting May 1, the previous mechanism will no longer be supported.

Recommended Handling Flow

The recommended webhook handling flow is:

Skulytics sends a webhook event to the registered endpoint.
The client endpoint receives the HTTP POST request.
The client validates and accepts the webhook payload.
The client immediately returns an HTTP 200 OK response.
Any additional internal processing is completed after the acknowledgment step.

Example Scenario

Registered endpoint:

https://companywebsite.com/skulytics_webhooks

This endpoint URL does not need to change.

However, the webhook handler behind this endpoint must be updated so that it returns an acknowledgment within 10 seconds and does not wait for heavy processing before responding.

Migration Summary

Clients should prepare for the following rollout:

April 23: the new webhook acknowledgment mechanism goes live
April 23–April 30: the previous mechanism is still available during the transition period
May 1: the previous webhook mechanism is officially removed

Before May 1, all clients should ensure that their webhook endpoint:

keeps the same registered endpoint URL
responds immediately to incoming webhook requests
avoids blocking the acknowledgment with heavy processing
returns acknowledgment within 10 seconds

The webhook retry schedule remains unchanged.