API Testing · /// Visual Flow Editor
API testing without scripts. Without compromise.
A visual flow editor with 21 executable nodes across a 28-node palette and OpenAPI / Swagger import. Author end-to-end API journeys in minutes. Replay as load tests AND as continuous synthetic checks. LoadGen brings API testing to the EUC/VDI world. Login VSI, ControlUp, and NeoLoad don’t offer this.
21 executable API flow nodesOpenAPI / Swagger importLoad + monitoring on one engine
Visual flow editor. 21 executable nodes, drag-drop, OpenAPI import.
The Problem
API testing usually means scripts.
Most API testing tools require scripting. Postman collections, k6 JavaScript files, LoadRunner VuGen projects, NeoLoad scripts. The script becomes the asset; the asset becomes the maintenance burden.
Script-as-asset gets brittle.
Scripts depend on environment-specific URLs, hard-coded values, and brittle setup steps. Six months in, the script library is more maintenance than the API it tests.
Load vs monitoring split.
The script that runs as a load test rarely fires as a monitoring check, and vice versa. Two scripts, two tools, two definitions of "working".
Non-developers can’t contribute.
When the API author has to be a developer fluent in the scripting language, the test library lives behind a knowledge wall. Product, QA, and ops teams can’t inspect or extend.
Why no-code API testing matters
Drag, drop, replay. Across modes.
A visual flow with 21 executable nodes across a 28-node palette. Flow control, request, data, control, assertion, and a Scriban-based built-in transformation node. OpenAPI / Swagger import. Author once, replay as load test AND as continuous synthetic check.
21 executable nodes, drag-drop
Flow control, request, data, control, assertion, and Scriban-based built-in transformation. Drag node, connect arrows, save. Flow authoring in minutes, not in a script project.
OpenAPI / Swagger import
Drop in an OpenAPI / Swagger spec; the flow editor scaffolds operations automatically. Author the user journey across the imported operations visually.
Load + monitoring, same flow
The flow authored once replays as a load test AND as a continuous synthetic check. One asset, two operational modes. No re-authoring across tools.
Author once, replay everywhere
The flow that ran as a load test also fires on a configurable schedule.
Most API tools require separate scripts for load vs monitoring. LoadGen unifies both. The visual flow authored in the editor replays as a load test AND as a continuous synthetic check. One asset library, two operational modes.
- Flow authored visually. Replayable as load AND as synthetic monitoring.
- No JavaScript or VuGen script to maintain.
- 21 executable nodes across a 28-node palette. OpenAPI / Swagger import.
- Same Analytics + AI surface across both modes.
Flow canvas. Multi-node visual API journey.
Capability
What ships with API Testing.
Visual flow editor (21 executable nodes)
Flow control, request, data, control, assertion, and Scriban-based built-in transformation. Drag-drop authoring, environments, and auth profiles.
Learn moreAPI debugger
Step through a flow live. See request, response, assertions, branching decisions per node. Debugging without running the full test.
Learn moreOpenAPI scaffolding
Import an OpenAPI / Swagger spec; the flow editor scaffolds operations. Author the user journey across the imported operations.
Learn moreLoad + monitoring replay
Same flow runs as load test AND as continuous synthetic monitoring check. No re-authoring across modes.
Learn moreAssertions + alerting
Per-step assertions: assert.status, assert.jsonpath, assert.schema, assert.latency, assert.contract. Alerts route to Email / Webhook / SMS / WhatsApp on failure.
Learn moreAnalytics & AI
AI-flagged response-time drift, error-rate anomalies, per-step regression scoring across every API execution.
Learn moreStep-through debugging
See each node execute, live.
The API debugger walks the flow node-by-node. See the request, the response, the assertion result, the branching decision. Debug without running the full test.
- Per-node request / response inspection.
- Assertion results visible inline. No separate test-result viewer.
- Control-flow decisions traced. See why the flow took which path.
- Debug in the editor; deploy the same flow to load + monitoring.
API debugger. Per-node step-through.
Proof
Numbers from the platform.
1.45M+
Tests run
across the customer base
1,000+
API endpoints
powering every module
8
Products, one platform
testing + monitoring + analytics + service levels
From €1,099
Per week · transparent
starts at 50 vUsers
Where API testing lives
Three API-testing jobs.
OpenAPI-driven API validation
Import the spec; the flow editor scaffolds operations. Validate the API journey end-to-end across imported operations. Replay as load AND as monitoring.
See use caseContinuous API monitoring
The same flow that validated the API as a load test fires on a configurable schedule as a synthetic check. Per-step latency, error rate, response-payload assertion. Alerted on regression.
See use casePipeline-gated API regression
Wire the flow into the deploy pipeline via the published REST API. Block deploys on assertion failure, latency drift, or error-rate regression.
See use caseAuthor an API flow on your own stack.
We’ll drag-drop a flow against your API in the visual editor on a call, fire it as a load test, and walk you through replay as a synthetic monitoring check.
Questions
Frequently asked.
What does the flow editor’s node palette cover?
A 28-node palette with 21 executable nodes: flow control (flow.start, flow.end, flow.call), request (request.operation for OpenAPI-driven calls, request.raw, request.replay), data (data.set, data.variable), control (control.if, control.switch, control.forEach, control.delay), assertion (assert.status, assert.jsonpath, assert.schema, assert.latency, assert.contract), and a Scriban-based built-in transformation node (transform.builtin).
Can the same flow run as load and monitoring?
Yes. That’s the primary design choice. The flow authored once replays as a load test (50–25,000 vUsers as a licence tier) AND as a continuous synthetic monitoring check on a configurable schedule. No re-authoring across modes.
How does OpenAPI import work?
Drop in an OpenAPI / Swagger spec; the flow editor scaffolds operations automatically. Each operation becomes a node template. Author the user journey across imported operations visually.
Can non-developers author flows?
Yes. The visual editor uses drag-drop authoring. Product, QA, and ops teams can inspect and extend flows without scripting expertise. The Scriban-based built-in transformation node is available for cases that need it.
What does no-code API testing cost?
API Testing pricing is provided on request. Load Testing is €1,099 per week at the 50-vUser tier and End-to-End Monitoring is €899 per Agent per month. API Testing is included in the multi-module bundles. Quoted on a call.
How does this compare to Postman / k6?
Postman focuses on developer-driven API testing in a desktop client; k6 uses JavaScript scripts. LoadGen ships a visual flow editor (no scripts), replays as load AND monitoring on the same engine, and is integrated with the EUC platform. LoadGen brings API testing to the EUC/VDI world; Login VSI, ControlUp, and NeoLoad don’t offer this.
