Webhooks

Server-to-server callbacks — you register a URL, the other system POSTs to it when an event happens (e.g. Clerk user events, payment provider events).

Why we need this / what value this brings

Lets an external system notify you the moment something happens, instead of you polling it repeatedly for changes.

When to use this

Integrating with any third party that supports event callbacks (Clerk user events, a payment provider's payment events).

How to use or implement this

Verify the webhook's signature before trusting the payload, respond quickly (2xx) and do slow work asynchronously after acknowledging receipt.

Research questions

• How does Localz verify a webhook actually came from Clerk/the payment provider (signature verification) and not a forged request?

---

Empty folder — drop notes, links, and findings here as you research.