Blog

Webhook engineering, in the open.

Field notes on signature verification, idempotency, delivery guarantees, and running webhook infrastructure in the EU. The code that came out of it is in our free open-source tools.

Flat illustration of Jira webhook filtering and delivery: a board of issue cards on the left throws cards into a funnel that stands for a JQL filter, only one card comes out of the funnel onto a cable that runs through the blue Webhooker pulse node, a stopwatch above the cable stands for the retry delay, and a row of envelopes reaches a server with a checkmark.

Jira Webhooks: Setup, Events, JQL Filters, Retries and Signatures

How Jira Cloud webhooks behave in production: admin webhooks, app webhooks and Automation web requests, setup in the UI and REST API, JQL filters and URL variables, the event list, the delivery headers, X-Hub-Signature verification in Python, the 200-only success rule, 5 retries spaced 5 to 15 minutes apart, the 30-minute rule, missing delivery logs, Data Center differences and local testing.

Flat illustration of a loop of calendar pages and paid invoices feeding the blue Webhooker pulse node, which branches to an open padlock with a key for a paid period and a ringing bell beside a cracked bank card for a failed renewal.

Stripe Subscription Webhooks: Which Events to Handle and When to Grant Access

The Stripe webhook events a subscription business actually needs: invoice.paid, invoice.payment_failed, customer.subscription.updated and deleted, trial_will_end and invoice.payment_action_required. The event sequence for sign-ups, trials, renewals, failed payments and cancellations, how subscription status maps to access, the invoice.created delay, the 2025 basil field moves, and a handler that syncs state from the API.