API now includes Webhooks

hen we announced the Testpad API, we said webhooks were coming. They're here. The API can now push events to you, so the moment something happens in your Testpad account, your other tools can know about it.

What a webhook does

A webhook is a message Testpad sends to a URL of your choosing whenever a particular event happens. Instead of your tools polling the API to ask "has anything changed?", Testpad tells them as it happens. You register a URL, choose the events you care about, and Testpad posts the details there each time one occurs.

Choosing what to listen for

Webhook events come in two groups: test runs and results. You can subscribe to a whole group, to a single event within it, or to everything at once.

• Test runs — a run is started, completed, or reopened
• Results — a result is recorded against a test: a pass, a fail, blocked, and so on

So you might take every result as it comes in, or narrow it down to just the failures. The full list of events is in the API documentation.

Connecting without writing code

You don't have to be a developer to use webhooks. Integration platforms like Zapier, Make, and n8n can catch a webhook and turn it into an action in hundreds of other apps. Point a Testpad webhook at one of them, and you can, for example:

• post a message to Slack or Teams when a test run finishes
• raise an issue in Jira (or another tracker) when results come in
• log results to a spreadsheet
• send yourself an email or a push notification

Getting started

The Testpad API is currently available on request, and now includes webhooks. To get set up, reach out to us at support@testpad.com. You'll find how to register a webhook, the full list of events, and worked examples in the API documentation.

If you liked this article, consider sharing