The APIs and the flows they power. Tested together.

Thunders generates, runs and maintains your API tests next to the UI flows they support. Describe the request, the expected response and the checks that matter. Thunders builds the test and keeps it working as your endpoints change.

Trusted by
PwC LogoSopra Steria LogoAllianz LogoSNCF Connect Logo

API testing catches what your UI tests miss.

Without Thunders
  • API checks written in a separate framework, maintained by a separate person
  • Response assertions hard-coded, brittle the moment the payload shifts
  • Auth tokens and environment variables managed by hand
  • No link between the API test and the user flow it supports
Thunders Logo
With Thunders
  • Describe the request and the expected response in plain language
  • Chain steps so one response feeds the next request
  • Validate status codes, fields and values without writing assertions by hand
  • API and UI checks live in the same test and run in the same pipeline

One platform for the request and the flow around it.

Most tools make you script the call and the assertions. Thunders builds the API step from a plain-language description and keeps it beside the UI flow it belongs with.

Generate in seconds

Describe the endpoint, the method, the payload and what a correct response looks like. Thunders builds the test, including checks on status, headers and response fields. It covers GET, POST, PUT, DELETE and PATCH, and handles no-auth, bearer token and basic auth for you.

Chain and validate

Pass a value from one response into the next request. Confirm the data returned matches what the flow expects, step after step.

Keep tests in sync

When the flow around an endpoint changes, update the whole test in one place, in plain language, rather than maintaining API and UI suites separately.

See it on a real flow: checkout with a payment API

Illustration of the 'Describe' step, writing a test scenario in plain language in Thunders

1. Describe

Log in, add an item to the cart, call the checkout API, confirm the order status is 'paid' and the confirmation page shows the order number.

Illustration of the 'Generate' step, Thunders building the test automatically from the description

2. Generate

Thunders builds the UI steps and the API step, with checks on the response status and the returned order ID.

Illustration of the 'Execute' step, the test running and returning a pass or fail result

3. Execute

The test runs the UI actions and the API call together, in your CI pipeline. Pass or fail report in minutes.

Illustration of the self-healing step, Thunders repairing the test after a change

4. Maintain

Next sprint the response adds a new field. Your existing checks keep working; add the new assertion in one line of plain language.

Plugs into your stack in minutes.

GitHub Actions, GitLab CI, Jenkins, Azure DevOps, Jira, Slack and Teams. Trigger API tests on every merge, next to the UI tests they belong with.

Illustration of Thunders integrating with CI/CD, issue tracking, and messaging tools

See more use cases

Ready to ship faster with smarter testing?