When we send a webhook to your server, your system responds with an HTTP status code.

We classify responses like this:

Example: 200, 201
This means your server received the webhook successfully.
👉 No retry is needed.

Example: 400, 404, 500
This means something went wrong.
👉 The system will retry sending the webhook.

If your webhook fails, we don’t stop immediately.
We retry multiple times using increasing delay intervals.

Here’s how it works:

✅ Maximum retries: 5 attempts

If all 5 retries fail, the event is marked as Final Failed.

A webhook will be automatically paused ONLY if both conditions below are met:

Failure Rate Formula:

(Final Failed Events ÷ Total Events) × 100

Example:

• Total webhook requests = 11

• Final failed events = 3

• Failure rate = 27.27%

Since 27.27% is more than 2%,

👉 The webhook will be paused.

Auto-pause will only be evaluated if:

• Total requests ≥ 10

If fewer than 10 requests are received,

👉 Webhook will NOT be paused.

Please note the following:

• Each webhook is monitored separately. (One webhook being paused does NOT affect others.)

• Auto-pause is calculated only after all retries are completed.

• Only final failed events are counted. (Retry failures are not counted individually.)

• A single success after failures does NOT immediately reset the failure count.

• Both total request count and failure count automatically reset after 48 hours. (Failure rate calculation starts fresh every 48 hours.)

Currently:

• YES email notification is sent.

• This feature will be implemented soon.

You can check webhook status by:

👉 Going to your client panel

👉 Open Webhook Configuration

👉 You will see pause status and reason there

To prevent your webhook from getting paused:

• Always return HTTP 200 for successful processing.

• Make sure your server responds quickly.

• Avoid returning 4XX or 5XX errors.

• Ensure your server has enough capacity to handle webhook load.