What actually happens when a webhook fires?
Most tutorials tell you "just add a webhook URL" but never explain what's actually going on under the hood. Let me break it down.
A webhook is just an HTTP POST request. That's it. When an event happens (someone pays, a repo gets pushed to, a form gets submitted), the service sends a POST request to a URL you control.
The request contains:
Headers — usually includes a signature so you can verify it's legit
Body — JSON payload with the event data (what happened, when, to whom)
Method — always POST
The tricky part? You need a URL that's actually listening. That means either spinning up a server, using ngrok, or...
Just use webhooks2.me. You get an instant URL, see every payload in real time, and actually understand the shape of the data before you write a single line of handler code.
I built this because I was tired of console.logging webhook payloads to figure out what fields were coming in. Now I inspect them visually, then write my code.
If you're learning APIs and integrations, this is the tool I wish I had on day one.
