Webhooks

Webhooks are extremely useful for staying up to date with changes in other systems but are they secure? This post will guide you through some steps to ensure the webhooks you consume are valid.

Keep your webhook verification settings around awhile by configuring them using an ngrok Cloud Edge. This post will demonstrate the process using the ngrok Dashboard as well as the ngrok-go library.

PagerDuty provides a shared secret with their webhooks so consumers can ensure the event's authenticity. Normally, verifying this secret requires a multiple step process implemented through your application code. This post will show how you can easily validate PagerDuty webhooks without making any changes to your code using ngrok's webhook verification feature.

This month we've been busy with ngrok-go, ngrok-rust, making OAuth and webhook verification free for all plans, and traveling coast to coast and even to Europe. Read on for details.

A few months ago, I had the opportunity to play with Zoom Apps. Before I dug in, I assumed Zoom would give an app a little information about an active or scheduled meeting, a little more on the user profile, let you manipulate a meeting, and call it a platform. Frankly, I couldn’t have been more wrong.

Webhooks are the foundation of modern API development. They enable us to react to changes in our systems, an incoming text message, a successful payment, or that latest pull request no matter our stack. While webhooks are universal in concept, they are unstandardized API contracts with few organizations paying attention to their design, security controls, and overall operational experience.

From the earliest webhooks at Twilio to every major SaaS platform, webhooks have become a defacto standard in web development. But before we can use them well, we have to use them correctly. Let's look at what that takes.