What are webhooks, and how can you use webhooks to push and pull data quickly in real time? Below, we’re answering these questions and more. This webhooks explained posts will show you everything you need to know about webhooks, including what they are, how they work, examples, and how to get started.

A webhook is an API concept growing in popularity. As more and more of what we do on the web includes events, webhooks are becoming even more applicable. These are incredibly useful and a resource-light way to implement event reactions.

What is a webhook?

So what exactly is a webhook? By definition, a webhook (also called a web callback or HTTP push API) is a way for an app to provide other applications with real-time information. A webhook delivers data to other applications as it happens, meaning you get data immediately—unlike typical APIs where you would need to poll for data very frequently to get it in real time.

This makes webhooks much more efficient for the provider and consumer. The only drawback to webhooks is the difficulty of initially setting them up.

Webhooks are sometimes referred to as reverse APIs because of the ability to give you what amounts to an API spec, and you must design an API for the webhook to use. The webhook will make an HTTP request to your app (typically a POST), and then you’ll have to interpret it.

How do webhooks work?

Consuming a webhook

The first step in consuming a webhook is giving the webhook provider a URL to deliver a request. This is often done through a back-end panel or an API, meaning you also need to set up a URL in your app accessible from the public web.

Most webhooks will POST data to you in one of 2 ways: as JSON (typically) or XML (blech) to be interpreted, or as a form data (application/x-www-form-urlencoded or multipart/form-data). Either way, your provider will tell you how it delivers it (or even give you a choice in the matter). The good news is both of these are fairly easy to interpret, and most web frameworks will do the work for you. If the web frameworks don’t, you may need to call on a function or 2.

Debugging a webhook

Debugging a webhook can be complex at times, as webhooks are principally asynchronous. Thus, you must trigger them and wait, then check the response. This can be tiresome and is fairly inefficient. Luckily, there are better ways. It amounts to the following:

  1. Understand what the webhook provides by using a tool like RequestBin to collect the webhook’s requests.
  2. Mock the requests using a tool like cURL or Postman.
  3. Test the code on your machine by using a tool like ngrok.
  4. Watch the whole flow using a tool like Runscope.

Securing a webhook

As webhooks deliver data to publicly available URLs in your app, there’s the chance that someone else could find that URL and then provide you with false data. To prevent this from happening, you can employ a number of techniques. The easiest thing to do (and what you should implement before going any further) is to force TLS connections (HTTPS). Once you’ve implemented that, you may go forward and further secure your connection:

  1. The first, and most supported, way to secure a webhook is to add tokens to the URL that act as unique identification, e.g.,?auth=TK.
  2. The next option is to implement Basic Auth—this is also widely supported and very easy to do.
  3. The third option is to have the provider sign each request it makes to you and then verify the signature—unlike the first two solutions, which work great to prevent most attacks but have the disadvantage of sending the auth token with the request. This has the disadvantage of requiring the provider to have implemented request signing—meaning if it doesn’t already, you’re probably out of luck.

Tips and best practices for creating webhooks

Here are a couple of things to keep in mind when creating webhook consumers:

  • Webhooks deliver data to your application and may stop paying attention after making a request. Meaning, if your application has an error, you’ll loser your data. Many webhooks will pay attention to responses and resend requests if your application errors out. So if your application processed the request and still sent an error, there may be duplicate data in your app. Understand how your webhook provider deals with responses to prepare for the possibility of application errors.
  • Webhooks can make a lot of requests. If your provider has a lot of events to tell you about, it may end up issuing a distributed denial of service on your app. Make sure your application can handle the expected scale of your webhook. We made another tool, Loader.io, to help with that.

Try webhooks with Twilio SendGrid

The best way to truly understand a webhook is to try one. Luckily, Twilio SendGrid is here to help you get started learning how to use webhooks, including how to even parse emails through our webhooks. For more information on SendGrid’s API, check out our docs pages.

Ready to start sending? Sign up for a Twilio SendGrid account to send 100 emails per day on our Free Forever plan.

Start sending emails with confidence

Create your free forever account
Expert advice and insight about all things email including best practices tips, examples, and advice for marketers, developers, and everyone in between.
Ayanna Julien
As Twilio SendGrid's Editorial Marketing Manager, Ayanna owns the quality assurance of blog content by focusing on authentic storytelling and editorial integrity. When not editing, Ayanna enjoys reading a good fiction novel or writing her own fiction.