our automated tests are passing (200 checks, green lights everywhere), but your stakeholders are still asking "is it ready yet?" Your CI pipeline gives you a pass/fail summary. Your manual results are already in Testpad. But getting both into one clear view still means tool-switching, exports, or just…not bothering.

The Testpad API changes that. Now you can push your automated test results straight into Testpad, where they show up in the same format as your manual tests. More than just a "200/200 passed" in a text file, but actual visibility into what's working and what isn't, all in one place.

What's an API?

An API (Application Programming Interface) is essentially a way for different software tools to talk to each other automatically. Think of it as a bridge that lets you write simple scripts to move data between Testpad and your other tools with no manual downloading, uploading, or copy-pasting needed.

What the API does (and doesn’t try to do)

With the Testpad API, you can script in Python, JavaScript, or whatever language makes you happy to:

• Push results in – feed your automated test outcomes straight into Testpad, right alongside manual runs.
• Pull results out – extract real-time progress and outcomes to power your own dashboards or reports.

Coming soon: webhooks. You’ll be able to fire off events from Testpad into Slack, Teams, or anything else that listens – perfect for notifying the team when test runs complete or triggering downstream processes.

Two big use cases we see already

1. Unified reporting
Your CI/CD pipeline runs automated tests. Your team runs manual ones in Testpad. Now you can pull both together into one view – push your key automated runs (release candidates, nightly builds, whatever matters to your process) straight into Testpad alongside your manual testing. There’s no need to juggle tools just to figure out whether you're ready to ship.

2. Custom dashboards
Need a big-picture exec summary? Want to track QA throughput week by week? Care about quality metrics over time? Use the API to pipe Testpad data into whatever reporting stack you already use.

How to get started with the API

For now, the Testpad API is available on request. If you want to try it out, reach out to us via support and we'll get you set up.

Once you have access, you'll need to generate an API token for authentication. Currently, only account owners can generate these tokens (we may expand this to account admins down the line, but for now we're keeping it limited to owners).

You'll find the full documentation at api-docs.testpad.com, where we walk through authentication, endpoints, and examples in Python and JavaScript.

Why this matters

The Testpad API is straightforward – a few clean endpoints that let you push results in and pull data out. It's built around how Testpad works, so if you understand Testpad's structure (projects, scripts, test runs), the API should feel pretty intuitive.

This is especially useful if your testing is already spread across multiple tools: unit tests in CI, manual checks in Testpad, managers asking for dashboards. Instead of forcing everything into one platform or manually cobbling reports together, you can now connect the pieces programmatically.

A shift for Testpad

The API documentation walks through authentication, endpoints, and examples in Python and JavaScript. It's a starting point – we'll add more capabilities as we see how teams use it and what's actually useful.

Want more practical testing advice? Subscribe to get straightforward tips on all things testing sent straight to your inbox.

If you liked this article, consider sharing