OpenAPI design, mocks, and load tests in one app

Design documents are first-class citizens in Ripple — stored locally alongside your collections. Edit specs in JSON or YAML with a document sidebar, run structural linting (Standard and Extended rule sets), and preview paths, servers, tags, and x-ripple-protocols extensions for gRPC, WebSocket, SSE, and GraphQL.

• Automatic version snapshots on save (up to 50) with restore from Versions dropdown
• Generate a collection from a design doc, or infer a design doc from an existing collection
• Export specs to disk; import .json, .yaml, .yml
• Richer export infers JSON Schema from request/response bodies
• Link a design document to a collection for design-to-implementation traceability

From the Design Studio, generate mock routes from your spec and launch a local HTTP server — CORS-enabled, path parameters, configurable delays. You can also maintain a standalone route table with GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD or wildcard methods, live request logs, and import routes directly from OpenAPI documents.

Mock backends run on your machine. No cloud mock quota, no monthly request limits — useful when Postman or Insomnia cap free-tier mocks.

Benchmark APIs from the same workbench. Configure concurrency and duration, point at a collection or single endpoint, and watch throughput and response-time metrics stream in real time.

• Multi-threaded execution with configurable duration
• Collection probe — bulk-execute saved requests to benchmark an API surface
• Live response-time analysis and throughput stats
• Son of Anton can draft load test plans from plain-English descriptions

A typical loop: author an OpenAPI spec → lint and preview → generate a collection → send real requests against a dev server → spin up a mock for frontend teams → run a load test before release. Request chains extract JSON paths into collection variables so multi-step flows stay in one workspace. The collection runner executes every saved request with CSV/JSON data files for parameterized runs.

• OpenAPI 2.0 / Swagger and OpenAPI 3.x
• Postman collections (export back to OpenAPI 3.0 JSON or YAML)
• WSDL for SOAP operation collections

OpenAPI Studio on the homepage · Ripple vs Postman · Full feature list