Before you write a webhook handler, it helps to see a real request. Which fields does the service send? Where is the event ID? What headers come with it? A sample payload in the docs is a useful starting point, but an actual event shows you what your integration has to work with.
That's why we built Adal Cloud Go, or Adal Go for short. Open go.adal.cloud, get a temporary HTTPS URL, and send a webhook to it. The request appears in your browser, ready to inspect. It's free, and there's no account to create.
Get a URL and send your first webhook
Getting started takes just a few steps:
Open Adal Go and select Get URL.
Copy the address into your service's webhook settings.
Send a test event, or perform an action that triggers a webhook.
Select the incoming request in the list to see its details.
There's nothing to install, and you don't need to run a local application. Use the URL as provided, or add a path and query parameters to match the request you want to inspect.
You can see the HTTP method, arrival time, path, query parameters, headers, and body. That gives you a way to check both the event data and the URL the sender is using.
See the payload before you build the handler
Suppose you're adding notifications for new orders. The provider's documentation includes an example JSON payload, but you want to know what it sends for your own test order. Which fields are populated? How are the nested objects structured? Where does it put the event type?
Add your Adal Go URL to the provider's test configuration, create an order, and open the request. You now have a concrete example to work from as you write your handler and check your assumptions about the format.
It's just as useful when checking an existing integration. You might want to confirm that the sender emits the right event type, includes an expected header, or sends requests to the correct path. You can inspect those details before connecting an application to process the event.
And if you're learning how webhooks work, Adal Go makes the connection easy to see: trigger an event in one service, then look at the HTTP request it sends.
A temporary URL for a quick inspection
Adal Go works while your browser tab is open and connected. It doesn't save webhooks for later or give you a permanent address. The latest 40 events remain in the tab's memory; there is no saved request history on the server.
Reloading an active tab clears the list and creates a new URL. You'll need to update the address in your sender's settings before sending more events. If the connection briefly drops, the same tab can reconnect to its existing address within 30 seconds, but requests missed during the interruption aren't replayed.
Each temporary URL accepts up to 60 requests per minute, with a maximum body size of 256 KiB per request. That's enough for inspecting individual events and running small batches of test requests.
Adal Go doesn't forward webhooks to another HTTP endpoint and doesn't work with Adal CLI. It lets you examine a request in the browser. For a persistent URL, saved requests, and delivery to your application, use the full version of Adal Cloud.
When you're ready to connect your application
Once you've explored the event format, you may need an address that stays the same, a request history you can return to, or a way to deliver webhooks to your application—including one running on your computer.
Create a free Adal Cloud account to take that next step. The full version provides persistent URLs for Servers in Adal Cloud, request storage for later inspection, delivery to HTTP endpoints, and Adal CLI support for applications running locally or in private networks. The documentation walks you through the setup.
You can get started for free there, too. After you verify your email address, your account receives 10 MiB of free traffic, refreshed every 30 days without rollover. Additional traffic is available to purchase when you need more. See traffic and billing for the details.
For a quick look at what a service sends, open Adal Go, grab a URL, and trigger an event. Your first webhook is ready to inspect right in your browser.