/// API testing tool
API testing that ends in code you own, not a collection you rent
Point-and-click request building for REST, GraphQL, SOAP, WebSocket, Kafka and gRPC — generated as a standard REST Assured + Cucumber project, with load, security and contract testing in the same seat, runnable without limits in your own CI.
Build requests point-and-click, get REST Assured you own
Compose REST, GraphQL or SOAP requests in the desktop API editor — or import a Postman collection or OpenAPI spec. Chain variables, add assertions, pick an environment.
Add WebSocket, Kafka (produce / consume) and gRPC steps (dynamic calls via server reflection, no .proto), data-driven CSV rows, load runs with SLA gates, security scans and Pact contracts.
One click writes a REST Assured + Cucumber Maven project with runner and CI files. Unlimited runs in your own pipeline; secrets stay in a gitignored local file.
Everything in one seat
Functional
REST, GraphQL, SOAP. OAuth2 profiles, status / JSON / XML / header / body / timing assertions, variable chaining, environments, Scenario Outline data runs.
Non-REST
WebSocket round-trips, Kafka produce and consume against a real broker, gRPC via server reflection. Heavy client libraries are added to the project only when a test uses them.
Load & security
Ramp / flow load tests with SLA gates; security scans mapped to the OWASP API Top 10 (injection, fuzzing, auth, JWT, headers), including scan-everything-from-OpenAPI.
Contracts & virtualisation
Pact consumer and provider tests; an in-process service-virtualisation stub with latency and fault injection so UI tests can run without live dependencies.
UI + API in one test
Log in through the browser, hand the session to an API step, assert the backend — the handoff nobody else tests, in one scenario.
Offline & air-gapped
Native Windows app, nothing leaves your network, signed offline keys. Generated tests only talk to the APIs you point them at.
Compared with other API tools
Common questions
Does it import my existing Postman collections?
Yes - Postman collections and OpenAPI specs import directly, so existing requests become the starting point for generated tests.
What is generated?
A standard Maven project: Cucumber feature files with your requests as steps, Java step definitions on REST Assured, a JUnit 5 runner, Jenkinsfile and GitHub Actions workflow, plus an Allure result set and Cucumber HTML / JSON reports.
Can it do load testing?
Yes - flow-based load runs with ramp profiles and SLA gates that fail the build, generated into the same project. Distributed multi-agent load is a deliberate non-goal; for that use a dedicated load tool.
Is there a run limit or cloud workspace?
No. You license authoring seats; the generated suite runs in your own CI as often as you like. There is no vendor cloud and no run meter.
What does it cost?
L3git API is $129 per user per month (annual); Suite with the UI recorder and the UI + API bridge is $169. A 14-day trial of the full product needs no key or card.