Developers

Read the webhook delivery log and retries

The delivery log is how you debug webhooks. 2xx is success; anything else retries on a fixed schedule until it gives up or you fix the endpoint.

4 of 5 in Developers

Webhook delivery log filters and status counts
Showcase book · Harbour Print & Signage (sample data) · light theme

On the Webhooks page, open the Delivery log.

Statuses

  • Delivered — your endpoint returned 2xx.
  • Queued — waiting to send.
  • Retrying — previous attempt failed; another try is scheduled.
  • Gave up — attempts exhausted.

Filter by event type and status when the list grows.

Retry schedule

Non-2xx responses retry up to 8 attempts, waiting 1 min · 5 min · 15 min · 1 hr · 3 hr · 6 hr · 12 hr between them. A 410 Gone stops immediately. After 5 deliveries in a row give up, the endpoint pauses until you resume it.

Deduping

Use PayBlah-Event-Id — it is the same on every retry and resend — so your consumer can ignore duplicates safely.

What this will not do

  • It will not rewrite your endpoint if DNS or TLS fails — fix the URL and resume.
  • It will not include PII in the payload; fetch details via API if your workflow needs them.

PayBlah is accounts-receivable automation software. You remain the creditor. Confirm local rules with your own advisor for your territory (US, UK, Ireland, or Australia).