Engineering, made clearer.Find a tool /
Learn · Practise · Understand

Learn Webhooks

Webhooks are event callbacks. Delivery may be duplicated or delayed.

3 sections · 10 explained questions · About 10 minutesAll lessons →

Read each short explanation, work through the example, then answer a pop quiz. Every answer explains the reasoning. Incorrect answers unlock a fresh question on the same idea; the full lesson contains ten questions.

01Understand the basics

Ready to learn

A webhook sends an HTTP callback when an event occurs. The sender can retry if it does not receive confirmation. Your receiver therefore needs to handle duplicate deliveries, verify the sender and preserve accepted work before responding.

Section 1 question · 4 variations
When should a queued webhook be acknowledged?

02Handle duplicates

Ready to learn

Use a stable event identifier to recognise deliveries already handled. Make the business action idempotent so that another delivery cannot accidentally charge or create something twice.

Try a different value

Move the slider or use the arrow keys to see what changes.
3 deliveriesVerifyDeduplicate ID1 business effect
Section 2 question · 3 variations
The same event ID arrives twice. What should happen?

03Verify and reconcile

Ready to learn

Verify signatures over the exact bytes required by the sender. Use timestamp or replay controls where supported. Periodically reconcile against the source if missing an event would matter.

Section 3 question · 3 variations
Which data should signature verification use?

Put it to work

Apply what you’ve learned using the related tools.