Skip to main content
A delivery is considered successful when your endpoint returns a 2xx within 25 seconds. Anything else — non-2xx status, network error, timeout — is treated as a failure and queued for retry.

​
What you should do

  • Return 2xx as soon as you have durably enqueued the event (e.g. written to a database or your own queue). Do not wait for downstream side-effects to finish.
  • Be idempotent. Use X-Notealy-Delivery-Id as a deduplication key. The same event can arrive more than once.
  • Stay under 25 seconds. Long-running work belongs in a background worker, not in the webhook handler.

​
What happens on failure

Failed deliveries are retried with backoff by Notealy’s queue. Persistent failures over a longer window may be paused; you’ll see them in the dashboard’s delivery log along with the response status and body we received. If a webhook subscription has been failing continuously, fix the receiver and contact us — we can replay missed events for a recent window.