POST to a URL you own the moment something happens.
Think of it like a mailbox. You give Quippy the mailbox address; every
time something interesting happens — an exam finishes, a user is
provisioned, a subscription changes — Quippy drops a note in that mailbox.
Why push, not pull
Without webhooks
- You log into a dashboard to check for updates.
- Or you ship a batch export / CSV every week.
- Your systems are always a little stale.
- Manual reports, delays, duplicated data entry.
With webhooks
- Exam finishes → your HR system knows within ~1 second.
- Grade posted → your gradebook updates automatically.
- New user provisioned → they appear in your CRM.
- No polling, no exports, no delays.
What Quippy guarantees
Signed
Every delivery carries an HMAC-SHA256 signature so your receiver can
verify the payload came from Quippy and wasn’t tampered with.
Retried
If your server is unreachable or returns 5xx, Quippy retries with
exponential backoff for up to 12 hours. After that, the delivery is
dead-lettered — visible in the admin portal and manually replayable.
Observable
Every delivery — status code, response body, timing — is logged and
visible per-endpoint in the admin portal.
Where to go next
Set up a webhook
Register an endpoint in the admin portal and capture the signing secret.
Verify signatures
The single most important page — how to check
X-Quippy-Signature in
your receiver before trusting a payload.Event catalog
Every event Quippy emits, with sample payloads.
Retries and delivery
How long Quippy keeps trying, and how to replay dead-lettered deliveries.