TestverTestver
API testing

API testing in the same place as your UI tests

Build requests, assert on the schema, chain the awkward parts and check contracts — beside your UI suites, with no browser to wait for.

Get started freeRead the documentation
REST & GraphQLOpenAPI & PactSchema checksChaining & mocksWebSocket · gRPC · Kafka
Testver — API
POST/api/cart/promoenv · staging
200 OK84 ms
{
  "code": "SAVE20",
  "orderTotal": "79.20",
  "currency": "USD"
}
Checks
status is 200
matches cart-schema.json
$.orderTotal is "79.20"
conforms to openapi.yaml
Seconds
No browser to startAPI checks return a verdict while a browser would still be launching.
One workspace
API beside UIThe same history and reports as your web and mobile suites.
From the spec
Not a blank pageImport an OpenAPI spec and the AI drafts the scenarios.
End to end

How API testing runs in Testver

  1. 1

    Import it, or describe it

    Bring in an OpenAPI or Swagger spec, an existing collection or a HAR file — or describe the API to the AI Assistant’s API mode.

  2. 2

    Set environments and auth once

    Environments plus bearer, basic, API-key and OAuth2 client-credentials auth, with mTLS and proxy settings per collection.

  3. 3

    Assert on the shape, not the status

    JSON-schema checks catch changes a 200 would hide. Extract values with JSONPath and script steps before and after a request.

  4. 4

    Chain, mock and load

    Feed one response into the next, stand up a mock for a service that is not ready, and load-test against percentile thresholds.

  5. 5

    Check the contract, gate the build

    Validate against your spec, diff versions for breaking changes, verify Pact contracts — and gate CI on framework API tests.

Collections or code — your call

API tests as code, in your framework

Plenty of teams want API tests in the same repo as everything else. Ask the AI Assistant and it writes them in your stack — REST Assured, pytest, Playwright’s request context — with the same auth, environments and assertions.

  • Written straight into your repo as framework code
  • REST Assured, pytest, Playwright request, C# HttpClient
  • Drafted from an OpenAPI spec or a plain-English ask
  • Run by your own build tool, and gated in CI

“Write an API test that applies promo code SAVE20 and checks the order total and the response schema.”

CartPromoTest.javaJava · REST Assured
@Test
public void promoCodeAppliesDiscount() {
    given()
        .header("Authorization", bearerToken())
        .contentType(JSON)
        .body(new PromoRequest("SAVE20"))
    .when()
        .post("/api/cart/promo")
    .then()
        .statusCode(200)
        .body("orderTotal", equalTo("79.20"))
        .body(matchesJsonSchemaInClasspath("cart-schema.json"));
}
What you get

Everything for API testing

OpenAPI and contract checks

Validate real responses against your spec, diff spec versions for breaking changes, verify Pact contracts.

Auth and environments

Bearer, basic, API key and OAuth2 client credentials — with mTLS and proxy support.

Chains and data-driven runs

Extract a token or an id, feed it forward, and repeat a flow over a data set.

Mocks for missing services

Scripted mock responses with request inspection, so you can test before a dependency exists.

Load checks

Concurrent requests with p95 and error-rate thresholds that fail the run.

Beyond REST

GraphQL, WebSocket, server-sent events, gRPC, Kafka and RabbitMQ — plus file uploads.

Your stack

Already using a framework?

Testver wraps it rather than replacing it.

PlaywrightREST AssuredpytestCypress

Also works with OpenAPI · Pact · C# HttpClient · supertest

Questions

API testing, answered

Do we still need a separate API client?

No. Requests, environments, auth, assertions and history live in Testver, next to your UI suites and their reporting.

Can Testver generate API tests from our OpenAPI spec?

Yes. Import the spec and the AI drafts scenarios from it; contract checks then validate real responses against the same spec.

Can we keep our API tests as code?

Yes. The AI Assistant writes framework-native API tests — REST Assured, pytest, Playwright request — into your repo, using the same auth and environments, and your build tool runs them.

Which protocols can it test?

REST and GraphQL over HTTP, plus WebSocket, server-sent events, gRPC, Kafka and RabbitMQ.

Web testingMobile testing
Quickstart

Start testing API in three commands

No account required to install, nothing to configure first, and your existing project works as-is.

1

Install it

One global npm package. Node.js 22 or newer (24 recommended) is the only prerequisite.

terminal
npm install -g @testver/testver
2

Go to your test project

Testver runs from inside the framework project you want to test, so change into that folder first.

terminal
cd path/to/your-test-project
3

Start the dashboard

Opens at localhost:3700. Testver detects the framework, language and structure of the project you started it in and lists your tests — no configuration to write.

terminal
testver serve

Typically under five minutes, start to first generated test.

Full installation guide — prerequisites, ports, running as a service
Ready to upgrade your test suite?

Keep your framework. Add AI and a premium toolset.

Set up in minutes. Self-host on your own hardware. Describe a test in plain English and get working code in your own framework — in a fraction of the time.

Get StartedSupport